Well, we made probably one of the most difficult choices halfway through Developing our Application, but it ended up being an easy decision. Here is our (somewhat) short story of making the transition from a Relational Databse (MySQL in our Case) to a Graph Database (Dgraph). Most of this post will …

Thanks for this. Still reading, but when I read this [image] amaster507: At this time, our GraphQL API resolvers were over 50K lines of custom hand written code and we were 6 months into development. Yikes.

this really depends on the complexity of the query and the filters. If we are talking subgraphs vs. JSON columns in MySQL, dgraph blows it out of the water (by being better). We did some smaller comparisons but I don’t have any of that data anymore. We wondered if a single row query by id with all …

Transitioning from a Relational DB to a Graph DB

Misc

kokizzu (Kiswono Prayogo) September 8, 2020, 12:59pm 4

how about the performance? any benchmark?

Topic		Replies	Views
Why you should build your next app with a graph database - Dgraph Blog Blog	4	1331	July 23, 2020
GraphQL atop a Graph Database - Dgraph Blog Blog	0	434	April 5, 2023
Building a Native GraphQL Database: Challenges, Learnings and Future - Dgraph Blog Blog	15	1717	April 26, 2020
SQL is slowing you down - Dgraph Blog Blog	9	3421	July 5, 2018
A History Lesson and Challenge for Dgraph Users, Developers, and Management team Users	8	1454	December 19, 2023

Transitioning from a Relational DB to a Graph DB

Related topics