I tried Hasura, the GraphQL API it generates is fantastic. However, you're still stuck with n+1 challenges with Hasura, plus you have to do a lot of table configuration. I don't need to set up Postgres tables, and carefully design my schema around potential performance bottlenecks in Dgraph—I just upload a .graphql file that lists all my types and it generates the API.
After using Dgraph for a few months, I really don't want to have to deal with relational databases again. Dgraph is the default persistence layer for anything I build now.
Great article! Have you considered alternatives like Hasura or Postgraphile before choosing Dgraph?
Thanks.
I tried Hasura, the GraphQL API it generates is fantastic. However, you're still stuck with n+1 challenges with Hasura, plus you have to do a lot of table configuration. I don't need to set up Postgres tables, and carefully design my schema around potential performance bottlenecks in Dgraph—I just upload a .graphql file that lists all my types and it generates the API.
After using Dgraph for a few months, I really don't want to have to deal with relational databases again. Dgraph is the default persistence layer for anything I build now.
Dgraph is the kind of the tech that is so amazing that it seems too good to be true, I'm blown away by it.
I'm considering it for my new projects. And Hasura for the ones that are already built with relational databases.
Thanks for sharing!