I’ve been slowing getting together a server based on Dgraph for the past few months after giving up on Firebase. My data greatly benefits from a graph structure but I couldn’t make it work well in a NoSQL document store and doing it in SQL was just clunky. I haven’t check in on the latest Dgraph news in a while but I just noticed Slash, along with the auth section in the GQL docs for Master and I have question/concerns.
Obviously based on my frustrations with Firebase, I’m excited at the prospect of a managed graph database server. But since following up on the GQL progress Dgraph has been making I’m worried about fragmentation.
I see an auth section under GQL. Is this only going to be available when using GQL and not GQL+? Unless I’m missing something, Slash only seems to support GQL with no GQL+ options available. Part of my schema relies on facets because of relationship-specific data. Are facets not supported on Slash? Is auth not supported on GQL+?
Are we looking at a Dgraph future where useful features are mutually exclusive based on what language you need to speak instead of having a full feature set with one language? Are there long-term plans to merge into one primary language (like GQL+ features on GQL) so features don’t end up getting splintered between them as they are now?
Yes, Auth just works for the GraphQL feature. I think (not so sure) that it works for basic GraphQL feature (not just Slash) but Slash has other things like integrations with third-party auth too.
Facets are not supported for now, but I think Slash already supports GraphQL+- on the schema. So you can use GraphQL+- and create your GraphQL Schema based on that. Until Facets being supported.
The Auth is another Story, I’m not 100% sure if you can use with the community version or if it is a Slash thing. I’ll ping @gja to answer this.
There are plans to make our GraphQL feature compatible as possible with Dgraph features. But as we don’t control the GraphQL Foundation, we can’t dictate what it goes in or out. And personally I think it might never happen to GraphQL Specs be similar to GraphQL+-. Cuz our lang is DB towards, and GraphQL is meant to meet a large share of users and their API needs. But I think we gonna be always close to GraphQL Specs. And you can always use Custom GraphQL+- queries in the GraphQL Schema.
Thanks @amaster507, that is right. You can now use DQL with Slash GraphQL. We are also currently working on supporting Dgraph in flexible mode, where’s you’ll be able to set up your schema with /alter endpoint as you would on a self hosted Dgraph (currently available if you ping us directly).