I was looking for a GraphQL endpoint backed by a graph database and found Dgraph.
Looking at this very long and amazing thread it seems that there are two primary users:
- developers looking for a robust and fast GraphQL endpoint with features that support a great developer experience
- database specialists looking for a robust and fast graph database with features that support a great database management experience
Both of these groups are also looking for:
- a serverless cloud experience
- a self-hosted experience
There are probably a couple of other user categories that would really be interested in Dgraph:
- no-code and low-code developers and platforms accessing a serverless cloud GraphQL endpoint
- UI and UX designers looking for an effortless way to enhance their prototypes - which are getting more and more sophisticated and merging into no-code and low-code solutions
- data analytics researchers
These last two groups are likely to use either Plugins available on their platforms, or go to an integration service like n8n.
What if Dgraph created, evolved and maintained a node designed to make it so easy to integrate with no-code and low-code platforms through another open-source integration platform like n8n?
Is there any reason why Dgraph cannot be a platform for both developers and database specialists?
Another consideration is to build on Dgraph’s developer features to also support a very compelling product for no-code and low-code builders. This kind of service could compete with RMDB based products like Xano: