I tried Dgraph a year or two before it went bust. I can confirm the query language mistake. The Graphql-alike was different enough to be unfamiliar, and still

I tried Dgraph a year or two before it went bust. I can confirm the query language mistake. The Graphql-alike was different enough to be unfamiliar, and still felt somewhat awkward to use. The other query languagewas pretty badly documented and also wasn't great. Cypher isn't perfect, but it's pretty decent. I also ran into a trivial bug around a comparison in a query not returning correct results and pretty much immediately gave up. (It don't remember the specifics, it might as well have been API misuse). But the biggest issue with all these graph databases for traditional application development is schema. Most of them are schemaless or have some half-assed, basic schema support. Nebula is the only one I can think of with proper schemas. This is not what you want for your primary data store! Even more so if logic is driven by JavaScript, or even Typescript since there are still plenty opportunities to mess up. I wish there was a proper multi-modal DB that combines the best of both the relationalnand the property -graph models. The recently announced SurrealDb might fit the bill. Graph stores are plenty popular for secondary workloads with special requirements, which is not dissimilar to Elastic search for the search domain. I don't see that changing anytime soon.