Meta tags:
description=NEO is a distributed, redundant and transactional storage designed to be an alternative to ZEO and FileStorage.;
keywords=ACID, ZODB, database, storage, nosql, distributed, transactional;

Headings (most frequently used words):

projects, neo, and, features, releases, latest, news, why, use, getting, started, documentation, scientific, publications, tips, tricks, tests, faq, licence, example, similar, related, project, architecture, characteristics, reliability, source, code, requirements, fuse, module, memcached, implementation, history, members,

Text of the page (most frequently used words):
neo (54), and (34), the (28), storage (22), for (21), zodb (14), not (12), data (12), nexedi (10), this (10), implemented (8), database (8), way (8), with (8), level (7), being (7), object (6), designed (6), cluster (5), zope (5), used (5), distributed (5), its (5), 2010 (5), code (5), disk (5), later (5), support (5), all (4), project (4), was (4), software (4), large (4), system (4), zeo (4), but (4), projects (4), scalability (4), memcached (4), server (4), using (4), test (4), too (4), transactional (4), following (4), transaction (4), free (3), top (3), 2009 (3), erp5 (3), client (3), caching (3), multi (3), transactions (3), very (3), related (3), fault (3), filestorage (3), there (3), other (3), both (3), does (3), started (3), write (3), back (3), published (3), find (3), see (3), one (3), than (3), long (3), tests (3), use (3), old (3), scale (3), are (3), protocol (3), systems (3), neoppod (3), pdf (3), list (3), features (3), note (3), can (3), source (3), checking (3), behaviour (3), expected (3), application (3), balancing (3), 2001 (2), since (2), then (2), tic (2), paris (2), lessons (2), learned (2), from (2), managing (2), petabyte (2), nodes (2), algorithm (2), atul (2), adya (2), consistency (2), optimistic (2), well (2), written (2), cap (2), wikipedia (2), some (2), pages (2), topics (2), design (2), file (2), interface (2), implementation (2), tolerance (2), similar (2), api (2), progress (2), benchmark (2), goal (2), end (2), instead (2), ram (2), etc (2), idea (2), when (2), testing (2), suites (2), fuse (2), module (2), core (2), might (2), terms (2), currently (2), stored (2), compression (2), array (2), persistent (2), through (2), investigated (2), replication (2), slow (2), non (2), pruning (2), changes (2), automated (2), com (2), choppy (2), hong (2), klai (2), petrucci (2), verification (2), petri (2), nets (2), linux (2), short (2), also (2), you (2), git (2), standard (2), reliability (2), such (2), ensure (2), quality (2), described (2), same (2), isolation (2), which (2), below (2), now (2), fit (2), updates (2), central (2), commit (2), done (2), load (2), first (2), nosql (2), cloud (2), june (2), demo (2), hosting (2), october (2), migrated (2), production (2), instance (2), internal (2), releases (2), version (2), over (2), multiple (2), machines (2), lock (2), revisions (2), optional (2), basestorage (2), maintained (2), legal, mention, 沪icp备14008524号, copyright, 2026, rights, reserved, members, initiated, 2005, french, company, developing, erp, small, enterprises, endorsed, competitive, region, feder, programme, european, union, history, dan, kegel, c10k, problem, yuanyuan, zhou, james, philbin, queue, replacement, second, buffer, caches, weak, generalized, theory, implementations, article, daniel, abadi, what, doesn, cover, brewer, theorem, petascaled, xrootd, scalla, page, databases, interesting, about, although, close, ceph, tolerant, clustering, servers, zeoraid, networked, rpc, directorystorage, relational, relstorage, single, best, our, knowledge, offering, preferred, otherwise, assigned, oriented, tools, original, ends, kumofs, may, stalled, cleaned, vincent, pelletier, time, unstable, stress, filesystem, wrapper, hard, partition, directly, actually, touching, they, strictly, dependant, example, licensed, under, rationale, please, licensing, gnu, gpl, licence, size, connected, zopes, 83724, stream, smaller, consumption, due, want, gradually, increase, ran, storing, million, rows, numpy, without, consuming, much, memory, doing, something, would, difficult, space, performance, wendelin, read, upload, 5tb, day, fluentd, slower, ethernet, speed, 20tb, becomes, out_of_date, syncing, synced, takes, mariadb, rockdb, did, number, going, 150tb, bottlenecks, issues, found, normal, running, stable, worked, include, reshaping, moving, how, compared, faq, results, stack, tips, tricks, christine, anna, dedova, sami, evangelista, silien, kais, laure, modelling, initial, bertrand, calonne, kordon, okuji, paviot, adet, smets, workshop, engineering, pnse, associated, poster, paper, 315, 316, scientific, publications, présentation, solutions, 2012, presentation, dresden, dzug, overview, introductory, dev, mailing, thread, contains, obsolete, information, specification, documentation, mysql, backend, innodb, rocksdb, tokudb, engine, chosen, early, approach, take, advantage, existing, basically, will, replaced, leaner, key, value, mysqldb, ssl, python, actual, requirement, epoll, integrated, plans, add, platforms, yet, required, requirements, pypi, get, repository, browse, online, github, mirror, https, lab, getting, functional, node, unit, individual, method, critical, process, formally, proven, relies, model, finally, seems, that, biggest, difference, between, sits, around, meaning, behavior, inside, provides, supposed, per, thesis, denomination, looks, stricter, shortly, here, deferral, focuses, interactive, rather, heavy, processing, moment, feature, priority, sequential, tapes, random, access, disks, requires, historical, current, accessible, needs, unsure, heavily, depends, duplication, update, pooling, happen, need, index, flushed, only, during, fine, grained, locks, better, helps, local, disc, cache, geographical, proximity, user, isn, distance, distribution, though, levels, special, intermediate, dynamic, static, side, thick, thin, growing, volumes, hindsight, additional, chracteristics, architecture, characteristics, why, march, press, release, discloses, open, 3rd, survived, nicely, public, where, were, shut, down, randomly, pull, plug, while, site, 17th, offers, plone, sites, part, their, service, objectis, trial, pilotsystems, 13th, 2011, www, shacache, org, 20th, 2015, latest, news, complete, detailed, changelog, april, 2019, increased, more, wide, adds, plan, extension, because, state, pending, deprecation, iterator, allows, exporting, conflict, resolution, pack, orphan, objects, undo, mvcc, implements, supports, extensions, redundant, alternative, developed, several, applications, including, websites, home,

Text of the page (random words):
neo home neo distributed transactional nosql for the cloud neo neo is a distributed redundant and transactional storage designed to be an alternative to zeo and filestorage it is developed and maintained by nexedi and is being used in several applications maintained by nexedi as well as nexedi internal production instance including all websites features neo implements zodb s storage interface and supports the following standard extensions revisions optional in basestorage with mvcc support undo optional in basestorage pack both pruning old object revisions and orphan objects conflict resolution iterator allows exporting storage data note there is no plan to support version extension in neo because of its pending deprecation state neo adds the following features no central lock no more storage cluster wide commit lock increased scalability load balancing over multiple machines fault tolerance data replication over multiple machines releases april 28 2019 version 1 12 see changelog for a complete and detailed list of releases latest news october 20th 2015 production instance of nexedi internal erp5 migrated to neo october 13th 2011 www shacache org migrated to neo june 17th 2010 pilotsystems offers free trial hosting code for plone 3 1 sites on a neo storage as part of their objectis hosting service june 3rd 2010 neo survived nicely its first public demo where some storage nodes were shut down randomly pull the plug way while using a demo site march 29 2010 system tic neoppod discloses first open source transactional nosql object database for the cloud press release why use neo architecture and characteristics with growing data volumes and lessons learned from managing a petabyte in hindsight below you can find additional chracteristics of neo thick client thin server neo designed this way client side compression neo implemented load balancing neo static balancing is done dynamic is not local disc cache data geographical proximity to user neo not implemented for now neo isn t expected to fit long distance distribution ram caching is done though both at neo and zodb levels neo level being implemented with a special intermediate caching algorithm fine grained locks are better neo designed this way and optimistic transaction consistency used in zodb also helps data flushed to disk only during commit neo designed this way no need for central index updates for object changes neo designed this way large updates update pooling neo this is not expected to happen at neo level but at application level ex zope data duplication neo designed this way sequential storage support eg tapes the same way as random access storage eq disks neo not implemented for now neo requires all data historical and current to be accessible to fit the needs of zodb it is unsure if this can be implemented at all and heavily depends on application level behaviour ex zope deferral system neo not implemented neo focuses on interactive use short transactions rather than heavy data processing long transactions for the moment so such feature is not on top of priority list finally it seems that the biggest difference between described systems and neo zodb sits around the meaning of transaction and expected application behavior inside a transaction neo provides the same level of isolation as zodb does which is supposed to be pl 2 as per atul adya s thesis denomination see below which looks stricter than transaction isolation shortly described here reliability the reliability of a data storage such as neo is critical to ensure the quality of neo design its protocol is in the process of being formally proven through model checking to ensure code quality neo project relies on automated testing unit test checking individual method behaviour functional tests checking node and cluster behaviour standard zodb test suites getting started source code you can get the source code in the following git repository https lab nexedi com nexedi neoppod git github mirror or browse it online it is also published on pypi requirements the following software is required linux 2 6 or later note the actual requirement is on epoll integrated in 2 5 44 there are plans to add support for other platforms but it is not implemented yet python 2 7 2 7 9 or later for ssl support mysqldb note mysql server is currently used as a backend for neo with innodb rocksdb or tokudb storage engine this was chosen as an early approach to take advantage of existing features transactional persistent storage basically and will be replaced with leaner key value storage later zodb 3 10 x zope 2 13 or later documentation protocol specification v1 old contains obsolete information introductory thread on zope dev mailing list a short neo overview as pdf presentation at dzug 2010 in dresden as pdf présentation à solutions linux 2012 à paris as pdf scientific publications verification of large scale distributed database systems in the neoppod project by o bertrand a calonne c choppy s hong k klai f kordon y okuji e paviot adet l petrucci and j p smets in workshop on petri nets and software engineering pnse 09 associated with petri nets 2009 poster paper pages 315 316 2009 the neo protocol for large scale distributed database systems modelling and initial verification by christine choppy anna dedova sami evangelista silien hong kais klai and laure petrucci tips and tricks tests automated test results are published on stack nexedi com faq q how does neo scale compared to zodb a for normal database use 1 tb neo is running very stable non scalability topics being worked on include pruning of old data being too slow and reshaping of a cluster neo moving data when cluster changes we did a number of scalability tests going up to 150tb to find bottlenecks issues found and being investigated replication too slow 20tb database one storage becomes out_of_date syncing this non synced storage takes too long for mariadb s rockdb read write upload 1 5tb day through fluentd was slower than disk ethernet speed being investigated the size of one neo server currently used and connected to 60 zopes is 83724 gb stored in erp5 data stream module on top of neo smaller disk consumption due to compression we want to gradually increase this 80 tb stored in zodb to 1 pb and ran one test storing an array of 4 9 million rows using wendelin core persistent numpy array in zodb without consuming too much memory doing something similar in zodb and filestorage would be difficult in terms of disk space and performance licence neo is free software licensed under the terms of the gnu gpl v3 or later for rationale please see nexedi licensing example projects projects directly related to neo but not actually touching its core they might or might not be strictly dependant on neo fuse module idea write a fuse wrapper using neo as a storage back end instead of a hard disk partition or cd etc goal stress testing with filesystem benchmark suites progress started in may 2010 stalled since then code to be cleaned up and published when i vincent pelletier find time unstable api zodb memcached implementation idea write a memcached server using neo as a storage back end instead of ram original memcached or other back ends kumofs etc goal benchmark with memcached oriented tools progress not started assigned api storage preferred otherwise zodb similar projects to the best of our knowledge there is no other storage interface implementation offering both scalability and fault tolerance the way neo does filestorage single file storage relstorage relational database storage directorystorage multi file storage zeo networked multi storage rpc zeoraid fault tolerant clustering of zeo servers ceph although not an object database its design is very close to neo related projects some interesting pages on topics related to neo but not written for about neo wikipedia page on object databases xrootd scalla a petascaled object database system brewer s cap theorem wikipedia and a very well written article on what cap doesn t cover by daniel abadi weak consistency a generalized theory and optimistic implementations for distributed transactions by atul adya the multi queue replacement algorithm for second level buffer caches by yuanyuan zhou and james f philbin used for client nodes zeo level caching the c10k problem by dan kegel lessons learned from managing a petabyte project history neo project was initiated in 2005 by nexedi a french company developing erp5 a free software erp for small to large enterprises implemented on top of zope since 2001 neo was then endorsed in 2009 by system tic competitive cluster by paris region and by feder programme of the european union members nexedi sa copyright c 2001 2026 all rights reserved 沪icp备14008524号 legal mention