If your data exceeds those amounts, then polyglot persistence is probably the way to go.
Is the other part of your data also interconnected and rich or is it just the social part? All that not only depends on the storage but also a lot on the use-cases and scenarions how you are going to use that data in the future. What kinds of apps, services, user(-requests) you have to server. If you need any support for a PoC don't hesitate to contact us. Cheers, Michael Am 24.11.2011 um 14:13 schrieb bm3780: > I'm struggling to determine whether graph is a good fit for my domain. Most > of my application is structured data. However, there are some parts that > are of a social nature and a graph seems like a good match. I guess my fear > is having all of the data in a single store, such as a graph, would cause > problems down the road due to the limitations. > > Potentially I need to go down the path of polyglot persistence...storing > just the social aspect of my data in the graph and storing the other data in > a document store. I was try trying to simply our architecture by using only > a graph, which would make O&M much easier down the road. > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/Neo4j-Data-Capacities-tp3533552p3533597.html > Sent from the Neo4j Community Discussions mailing list archive at Nabble.com. > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
