I would say whenever the data set cannot fit on a single machine. This is not a definitive nogo as you can always shard the data yourself and spread across several (preferably co-located) Neo4j instances but this is far from ideal in most cases, I guess.
On Saturday, 9 May 2015 11:07:15 UTC+2, Tim F wrote: > > Hi all, > > I'm authoring some training on Neo4j and would like your input on when you > think Neo4j would not be the best candidate for persistence. > > I have some ideas already, but I'd like to get the community's input. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
