On Tue, Aug 18, 2009 at 15:02, Dennis Peterson<dennisbpeter...@gmail.com> wrote: > Just curious, is there anything else people are doing with Neo4J to meet > high-availability requirements?
Two architectures seem to have emerged: a) Add a REST layer in front of your Neo4j backend. That REST layer speaks the domain language (i.e. Persons, Cars, Images rather than Nodes, Relationships, etc) and it pushes mutating messages onto some form of a queue (something like ActiveMQ/RabbitMQ/Tibco/SQS) which is propagated to the backing Neo4j instances. Read requests are dispatched to one of the instances. We have a number of commercial customers that use this setup. b) Use the online backup to create a warm spare. That warm spare can be used to create infrequently synchronized read-only slaves (updated maybe hourly or something like that). Cheers, -- Emil Eifrém, CEO [e...@neotechnology.com] Neo Technology, www.neotechnology.com Cell: +46 733 462 271 | US: 206 403 8808 http://twitter.com/emileifrem _______________________________________________ Neo mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
