From vincent at nexedi.com  Mon Aug 27 14:37:37 2012
From: vincent at nexedi.com (Vincent Pelletier)
Date: Mon, 27 Aug 2012 14:37:37 +0200
Subject: [Neo-dev] [announce] NEO 1.0 - scalable and redundant storage for
	ZODB
Message-ID: <20120827143737.2bc1a837@vincent-tkpad>

Hi,

We've just tagged the 1.0 NEO release.

NEO aims at being a replacement for use-cases where ZEO is used, but
with better scalability (by allowing data of a single database to be
distributed over several machines, and by removing database-level
locking), with failure resilience (by mirroring database content among
machines). Under the hood, it relies on simple features of SQL
databases (safe on-disk data structure, efficient memory usage,
efficient indexes).

Release highlights:
- production-ready !
- asynchronous replication across clusters, for inter-datacenter
  redundancy
- there will be no further expensive data schema changes within the 1.x
  branch as there were in 0.x branch
- replication performance is significantly increased
- general implementation performance improved
- several bugfixes

What you need to know if you are used to ZODB features:
- Blob API is not implemented yet.
- pack's GC phase will not be implemented in NEO, it relies on
  zc.zodbdgc for this: http://pypi.python.org/pypi/zc.zodbdgc

For more details, look at README and CHANGES included with the sources:
  http://git.erp5.org/gitweb/neoppod.git/blob/HEAD:/README
  http://git.erp5.org/gitweb/neoppod.git/blob/HEAD:/CHANGES

NEO is published on pypi as "neoppod":
  http://pypi.python.org/pypi/neoppod

Regards,
-- 
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises


From regebro at gmail.com  Mon Aug 27 14:46:53 2012
From: regebro at gmail.com (Lennart Regebro)
Date: Mon, 27 Aug 2012 14:46:53 +0200
Subject: [Neo-dev] [ZODB-Dev] [announce] NEO 1.0 - scalable and
 redundant storage for ZODB
In-Reply-To: <20120827143737.2bc1a837@vincent-tkpad>
References: <20120827143737.2bc1a837@vincent-tkpad>
Message-ID: <CAL0kPAUVq4NNrmSnsBWU=PqrZXs6XHCMCKGp2C8EAFJSJWR3ag@mail.gmail.com>

On Mon, Aug 27, 2012 at 2:37 PM, Vincent Pelletier <vincent at nexedi.com> wrote:
> Hi,
>
> We've just tagged the 1.0 NEO release.
>
> NEO aims at being a replacement for use-cases where ZEO is used, but
> with better scalability (by allowing data of a single database to be
> distributed over several machines, and by removing database-level
> locking), with failure resilience (by mirroring database content among
> machines). Under the hood, it relies on simple features of SQL
> databases (safe on-disk data structure, efficient memory usage,
> efficient indexes).

That sounds pretty cool!