It is not easy for a beginner to learn to use Neptune. You would need prior knowledge of graph data or similar concepts. It's about having a basic understanding. Opting for this solution totally depends on your parameters. One parameter is definitely the cost. For a single instance, the monthly cost of Neo4j is $65 without the visual representation and over a hundred with it. In terms of AWS, it's around $10 to $20 a month. So, from a cost perspective, you should go with Neptune. It gives a similar performance to Neo4j. Also, consider if your developers have a good understanding of the graph data structure they are going to implement in the graph database. If so, I think Neptune is a fine tool. Overall, I would rate the solution a nine out of ten.
Senior Database Administrator at Summa Health System
Real User
2022-03-30T18:41:00Z
Mar 30, 2022
My advice to others wanting to start using Amazon Neptune would be to start small and it is more geared toward the developer that's creating the website. For example, if they were creating a LinkedIn website, they are going to use that type of database, there's is not much more to do. These databases are geared more towards developers where DBAs don't have much to do with the Neptune type database. I rate Amazon Neptune a nine out of ten.
Amazon Neptune is a fast, reliable, fully managed graph database service that makes it easy to build and run applications that work with highly connected datasets. The core of Amazon Neptune is a purpose-built, high-performance graph database engine optimized for storing billions of relationships and querying the graph with milliseconds latency. Amazon Neptune supports popular graph models Property Graph and W3C's RDF, and their respective query languages Apache TinkerPop Gremlin and SPARQL,...
I recommend Amazon Neptune and hope it allows querying languages other than Gremlin. This will enhance its integration capabilities.
It is not easy for a beginner to learn to use Neptune. You would need prior knowledge of graph data or similar concepts. It's about having a basic understanding. Opting for this solution totally depends on your parameters. One parameter is definitely the cost. For a single instance, the monthly cost of Neo4j is $65 without the visual representation and over a hundred with it. In terms of AWS, it's around $10 to $20 a month. So, from a cost perspective, you should go with Neptune. It gives a similar performance to Neo4j. Also, consider if your developers have a good understanding of the graph data structure they are going to implement in the graph database. If so, I think Neptune is a fine tool. Overall, I would rate the solution a nine out of ten.
My advice to others wanting to start using Amazon Neptune would be to start small and it is more geared toward the developer that's creating the website. For example, if they were creating a LinkedIn website, they are going to use that type of database, there's is not much more to do. These databases are geared more towards developers where DBAs don't have much to do with the Neptune type database. I rate Amazon Neptune a nine out of ten.