I have looked at NEO which is the closest thing I've found to the
answer, in fact NEO is why I felt Plone was the best choice of CMS to
inquire further about
The problem is that it uses SQL for its indexing queries (they quote
"NoSQL" as meaning "Not only SQL"). SQL cannot work in P2P space, but
can be made to work on server-clusters.
We intend not to have any machines in our network other than the users
computers running the P2P application. So we would need to know exactly
what kinds of querying ZODB expects to be available in its interface to
the storage layer. DHT's can be slow for the first read but cache
locally after that.
On 04/01/11 20:06, Andreas Jung wrote:
> Marc Villemade wrote:
>> Hey Andreas,
>> I think it makes sense if the storage backend is hosted on-premise (hence
>> private cloud), and i think that's what Aran is thinking about.
>> They could have Plone->ZODB->Storage backend in the same datacenter, hence
>> no latency problem and good network throughput, provided that the cloud
>> storage used is capable of offering high performance.
> First you should bring up arguments why the existing backends like ZEO,
> Relstorage or NEO are not good enough in your case. Looking at the
> development history of Relstorage or NEO: implementing an
> enterprise-level storage for the ZODB seems to be hard and
> time-consuming (and expensive).
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org