Hi, Currently considering neo4j. We know a graph DB is the right solution long term, but we need to get our app out fast and with minimal infrastructure overhead.
We won't hit performance issues on SQL for at least 6 months, and we're iterating weekly, so while that may seem close, using unfamiliar tech would slow us down. We're currently work with rails3 on heroku, which is postgres. We have some experience with recursive PostgreSQL queries and none with any NoSQL databases. What's the learning curve like, and how hard is transitioning a SQL array list to neo4j, which we'll need to do if our app is a success? The data structure we want a graph for is a Directed Acyclic Graph). We can implement the basics fairly easily in postgres, but recursive lookups will be a pain to write and costly to run. Thanks, Ben Sand _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
