The majority of developers probably use a rest api, which graphql is a huge improvement on if you have relational data (especially with local caching etc).
I didn’t say only advanced users. In fact, I would say most real advanced users will write their own custom middleware (so quite the opposite), although one part of this middleware is probably in GraphQL.
This is just my opinion, but I don’t see how. You can easily use DQL without DGraph GraphQL. I think the majority of DGraph’s users don’t use the GraphQL middleware, but I have no idea as far as DGraph Cloud users, the paying users.
That being said, the product they’re selling is not solely a Graph Database. I agree with @CosmicPangolin1 that if they can’t support two eco-systems, they need to choose.
The people that use GraphQL don’t really care about GraphQL in-and-of-itself. They care about the middleware, which most DbaaS do NOT provide outside of the box (I spoke about this somewhere on here). GraphQL allows for caching on the front end, and is made for querying graph data.
Either way, the most important thing is that it is too costly to start all over at this point. They are 80% of the way there with GraphQL (it is probably impossible to get to 100%, but a few features we have listed can go a long way).
J