From vincent at nexedi.com Thu Jul 18 15:51:38 2013 From: vincent at nexedi.com (Vincent Pelletier) Date: Thu, 18 Jul 2013 15:51:38 +0200 Subject: [Neo-users] Is NEO the future? In-Reply-To: References: Message-ID: <20130718155138.48bd8f76@vincent-tkpad> Hi. Sorry for replying so late. I reordered a bit your mail to make it easier to reply to. On Wed, 10 Jul 2013 22:25:49 +0900, Chao Meng wrote : > Hi NEO developers, > > First of all I would like to thank you for all your effort on making NEO in > production! From the pdf doc I can find on NEOPPOD website, the design > looks suitable for my needs. > > I am basically a huge fan of python and ZODB, beginner though. Currently I > am using ZEO for database part of my website, but facing server side > replication issue when having more than one server for the website. And > then NEO comes to me after some search online. It seems to me the right > solution over RelStorage. [...] > MangoDB and CouchDB are very popular these days, but to me ZODB is THE pure > oodb. Thanks for sharing our point of view on what features ZODB server should provide. I would add that "lesser" oodb lack nice transactional support that ZODB requires. This is a way to gain performance and make the database engine easier to promote. But the flip side is that it pushes complexity in the hand of application developers, which need to go out of their way to implement a lock here or there to protect their data. This just belongs to the database instead of standing in the way of contributors. > However, I couldn't find any use cases or active > user/developer population. I am a bit worried about the NEO community. [...] > Do you know any use cases with NEO 1.0? > > How big is the user population and dev population? shacache.org uses NEO to hold between 400GB and 600GB of data. It is a caching site used by our software deployment suite, SlapOS[1]. NEO works very well for this site, but we aren't pushing it in its limits yet: two storage nodes without replication, a one-node asynchronous replication cluster as backup, application being poked at mostly by scripts instead of serving web pages to humans. NEO is becoming the standard backend for ERP5 as a replacement to ZEO. We are currently migrating our internal ERP instance (which is using our flagship product, ERP5, which is a Zope-based ERP) to NEO. It will be used to host one of our large customer project (tens of millions of persistent objects, 60khits/hour of human-generated traffic with peaks at 125k, 16 Zope processes - some for automated computations, some facing users) to NEO. This is expected to happen in the coming 6 months. So NEO does work for us, and it is definitely our future. > Any plan to do some marketing on NEO/ZODB? It has been presented on zodb-dev, and Jim Fulton expressed interest in the design, but was concerned about GPL licensing (Zope uses BSD-style licensing). I also made two presentations, for which I produced the presentations you found as PDFs on the site: DZUG 2011 and Solutions Linux 2012. But other than this, we prefer to invest our available resources in NEO's code than sponsoring - I'm personally much more competent at typing stuff than at hyping stuff. [1] https://www.slapos.org/ Regards, -- Vincent Pelletier ERP5 - open source ERP/CRM for flexible enterprises