mrjn
November 9, 2021, 10:48pm
9
Tell me what you guys need Dgraph to be. Let’s create a list of things that it should be. And, then let’s figure out how you guys can help us achieve those things.
6 years ago, I set out to build an application database backed by graph engine. But, we haven’t reached there yet – Dgraph is still not an application DB. I’m curious to hear people’s thoughts about what is lacking for Dgraph to become an application database.
Is it lacking performance?
Do you really need transactions?
Should Dgraph not be a database? Should it be a serving system instead?
Should Dgraph interface with other databases better?
Does Dgraph not work with GraphQL properly? or React…
3 Likes