<br><br><div class="gmail_quote">On Wed, Mar 31, 2010 at 3:32 AM, Vincent Pelletier <span dir="ltr"><<a href="mailto:vincent@nexedi.com">vincent@nexedi.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi,<br>
<br>
I would like to present you the NEOPPOD project, aiming at improving ZODB<br>
Storage scalability. The implementation is in a rather good shape, although it<br>
fails at a few ZODB tests at the moment (they are currently being worked on).<br>
Scalability is achieved by distributing data over multiple servers<br>
(replication and load balancing) with the ability to extend/reduce cluster<br>
on-line.<br></blockquote></div><br>Congrats! <br><br>A few questions that you may want to add in a FAQ.<br><br> - NEO replaces FileStorage? Maybe typo?<br> - What is the gain of using NEO over relstorage + mysql replication?<br>
- Why not include ZODB 3.10/Python 2.6 as a goal of the project?<br> - I understand *today* the technologies use python 2.4 but <br> ZODB 3.10/Plone 4/Zope 2.12 use python 2.6<br> - NEO is a different protocol than ZEO?<br>
- What is the Blob story with NEO?<br> - Any issues with 32bit vs 64bit<br> - Backup/restore strategy of NEO<br><br>Other notes:<br> - Maybe explain the goal of the project clearer:<br> """<br> NEO provides distributed, redundant and transactional storage
designed <br> for petabytes of persistent (python?) objects.<br> """ <br> - A buildout for NEO would lower bar for evaluation<br> - How do you plan on storing petabytes in a single MySQL server? since<br>
that is the data structure backend for NEO? <br><br>Looking forward to reading the petrinet article - please send update when<br>it comes out. <br><br>cheers<br>alan<br>