Dgraph Reviews in January 2025: User Ratings, Pros & Cons

"Graph DB implementation of SCIM Protocol for Cross Domain Identity Management for Enterprise Clients"

What do you like best about Dgraph? A very accessible graph DB solution. Ratel dashboard at play.dgraph.io allows one to become quickly familiar with the syntax. Set up on k8s. The team is very responsive and helpful in the case of issues or inquiries. Recurse option to return nested levels in the tree. Compatibility with Go and tracing to identify bottlenecks. Metadata on the queries to see how many nodes were touched.

"Blazing fast Database"

What do you like best about Dgraph? The Dgraph product is super lite weight and very fast in performance in querying across millions of edges. Dgraph Team is a very dedicated in solving the needs of the us and helping us in making sure our product is build right way and providing insights and improvements. This help us in a big way in using Dgraph in our solutioning. Dgraph support is exceptional and many thanks to Daniel Mai from support team. Very professional team and smart engineering team.

"High speed software development due to the power of Dgraph"

What do you like best about Dgraph? I am a big fan of DQL. At Mooncamp we use it in every part of our application, and it feels like Dgraph built the missing parts to GraphQL. Furthermore, I love Dgraph's facets. We use it to store information such as the order on edges. This used to be very complicated to model in relational databases and is now so easy with Dgraph.

"Intuitive way to manage your data"

What do you like best about Dgraph? My favorite part of DGraph is that they use GraphQL +/- as their query language because I'm able to easily get back exactly what data I need without having to write complex joins.

"A simple solution for a complex problem"

What do you like best about Dgraph? Dgraph has been absolutely instrumental in solving complex issues on widely used internal tools within Comcast. Having full GraphQL compliance on top of DQL (Dgraph Query Language) has made building robust dashboards with ease without sacrificing performance. One of our hardest problems to solve was building a la carte queries with complex reverse references and deep relationships. With Dgraph it solves all of those needs without having to build out ...

"Modern database with a great developer experience"

What do you like best about Dgraph? In our experience, Dgraph has made graph databases accessible for everyone and has convinced us to migrate our mixed-use databases to Dgraph. The documentation is great, but the community forum is even better! We have regular contact with the development team on specific feature requests. The pricing is also very attractive for smaller projects; even if they grow bigger it will still be affordable. The free tier makes it easy to start small and expand ...

"Flexible and scalable"

What do you like best about Dgraph? Dgraph provides flexible and custom data resolvers that allow us to integrate it with other services, database and technologies. It does this in parallel, allowing almost infinite scalability and massive performance gains. With its own DQL (extension of GraphQL), you can pass variables between graph queries and use the results of previous queries in future segments.

"A great GraphQL Native Graph database"

What do you like best about Dgraph? While Dgraph ships with many features, what I like the most is: - The ability to use all GraphQL tools with it since it natively uses GraphQL

"Quick and easy, one of the best GraphQL cloud databases there is"

What do you like best about Dgraph? I liked how simple it is to set up. The interface is simple and easy to navigate and even as someone who has never used GraphQL before is able to learn to use it very quickly. I was able to do everything on the platform including managing the schema, importing data, exporting data, creating security keys, and more.

"DGraph: a rising star in the database landscape"

What do you like best about Dgraph? - Very simple to run. With native GraphQL support, one just has to define a schema and begin consuming the database from client side. It's a huge productivity boost as one doesn't have to spend time building table schemas, writing ORM mappings and API definitions.