4 ms·
I'm not doubting the popularity of the bindings, more the ability to scale it. The most popular argument against NoSQL solutions is the limited amount of info a
by nchuhoai 15y ago
I'm not doubting the popularity of the bindings, more the ability to scale it. The most popular argument against NoSQL solutions is the limited amount of info and expertise available to build a strong and scalable system with them. Even now with extremely popular solutions like Mongo, people are still not too sure whether the apparent performance boosts are worth the issues in the long run
I am aware of the Heroku addon, but what happens if you need more than that?
- akollegger 15y agoThe current cluster is a master-slave replication configuration, for read scaling. For write scaling, you would have to stay tuned. There's a team sequestered in England feverishly working on a sharding solution to spread write load and data set size across multiple machines without compromising query performance. Heroku is just the first cloud service to offer Neo4j. We've been chatting with other PaaS providers, and some are moving forward with their own plans. A few enterprise customers simply orchestrate their own clusters (up to global, multi-continent spanning deployments) using EC2. You're right that all of the NOSQL solutions don't have as many experts and professional services as the relational db options. Seems like a great opportunity. ;)
- nchuhoai 15y agoThanks for the state of Neo4j. I really love Neo4j, but I am just afraid I'm hurting myself in the long-run, because I definitely don't like sys-ops, so I feel like I need to revert to more conservative solutions.