Hello Nick!
I think dgraph will focus on the two first categories while the no-code low-code will be done by “intermediaries”. Dgraph should probably focus on its DB and its cloud service, the performance and DX, while an intermediary can focus on low-code prototyping and data-analysis
Here is a summary of dgraph key missing features and issues that @jdgamble555 and @amaster507 made:
At Blitz (YC S22) we are actually becoming one of those intermediasries for the other usr categories that you mention (https://www.blitznocode.com/)
We are building an abstraction layer over dgraph so non-developers can create a data model and pair it with workflows and an interface builder. With zero code! (It sounded like an Ad but is just me being hyped about by my own product lol)
So imagine a baby between xano/airtable + n8n/integromat + retool/stackr that a non-tech operations manager or entrepreneur can use to build tools or prototype new features.
I think that’s the right way to go, splitting the different types of customers with different types of products. So each one can focus on delivering the best value to their segment.
We are also developing a graphQL alternative (blitzQL) which works diretly in JSON format instead of strings, where we will be able to filter nodes by children props as well as editing children nodes from their parents, or cascade deletes. Eager to share more about this soon 