![]() I think they're probably waiting to see if graph DB rise in popularity before committing developer resources or they already know they can't compete with Neo4j so they're going to let their DB flounder for anyone who doesn't want to use it. I think they found an open source engine that they could tweak and rebrand to check off the box that they have a graph DB but I don't think they're committed to their DB. Neptune has also only had 4 software releases, v1.0.1.0, v1.0.2.0, v1.0.2.1, v1.0.2.2 which doesn't show to me that AWS really cares about this DB technology. You'll easily eat up development time trying to debug random crashes than spending a day in configuring a backup schedule and EC2 autoscaling policies. Unfortunately I don't have of those links saved of the performance but I read enough to convince me that no matter of "reduce work of backups" am I going to sacrifice actual query performance and have my application randomly crash. I found people who did benchmarks and found that Neptune would even crash when their graph got to a certain size and the query tried to do more than N-number of recursive traversals. I couldn't find anyone who has had a positive experience using Neptune. Since my original post I started doing more research to find performance benchmarks and user experience. This is where I'd ask how volatile is the traffic is your traffic to the database and are you're seeing huge fluctuations in your traffic patterns that a severless service is warranted. ![]() Adobe is running their Behance product on Neo4j and they have tens of thousands if not hundred of thousands of users all stored in a 3-node Neo4j cluster. With an enterprise license you can run a cluster and scale horizontally. Once you have them being taken it's almost zero maintenance.Īuto-scaling also can be solved with just a little more DevOps work. ![]() It's been my experience, getting back ups scheduled and running is one-time task. That's the argument that the people trying to convince me that moving to AWS is better than Neo4j, they say it's worth not having to worry about backups and auto scaling.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |