Victor,
for scaling out, there are two approaches that we see people using to
scale Neo4j:
1. Use HA to replicate several Neo4j instances
High Availability as a Master-Slave scenario with Master failover is
currently in QA, but is planned to be released as part of Neo4j 1.2
and merged into the
Peter,
Thank you very much for the info, it helped a lot.
I entirely agree with HA being a much better approach to scale out Neo4j and
I'll see to implement it ASAP to give you some feedback. Currently the
project is entering staging mode and as I do some benchmarks I'll see when
to use HA and
Sorry Peter for the late reply (and the clumsy first email).
I drew a very very simple diagram exemplifying the architecture, I don't
know if the list will support the attachment so if it doesn't, warn me :P
As you can see by the diagram, my neo4j DB is running inside the REST app
that will read
Victor,
sorry, I am not entirely understanding your domain so I can't say
anything for sure. Do you have some architectural diagram and/or some
example flow in order to better understand?
Sorry for the inconvenience
Cheers,
/peter neubauer
VP Product Development, Neo Technology
GTalk:
Hey folks,
I'm actually developing an application that requires maintaining following
relationships between nodes, another application reads out those
relationships and take the steps to perform notifications about actions to
some entities.
That said, I got a doubt about the best design to
5 matches
Mail list logo
