Building an API around Dgraph application

[MichelDiz]

@forstmeier

What is the difference between “regular” GraphQL and GraphQL±?

GraphQL+- is inspired in the “pure” GraphQL. In structure, they are very similar, but Graphql+- has “forked” a lot from Graphql’s specs. You can read more I can say about it here V2 and grphql vs graphql+- - #2 by MichelDiz

@forstmeier

If there’s a notable difference, is it only possible to use the supported clients (e.g. Go) to run GraphQL queries/mutations and not “regular” GraphQL?

All clients created by Dgraph runs only GraphQL+-. For “Pure GraphQL” you have to use any the several GraphQL clients out there. Like the ones from Apollo.

@forstmeier

can you help me understand the difference between the documents discussing the Dgraph query language?

The link from other conversations can explain the difference between the two languages. The docs I’ve shared are about start running the Graphql on Dgraph. I’m not sure what else to say about it.

@forstmeier

I’m definitely interested in the documentation you provided because defining the schema in “pure” GraphQL seemed to be more in-line with what I’m looking for where types are explicitly linked as predicates on other types in the definition.

Cool, We have no specific documentation on Graphql. You need to read the documentation for the Graphql spec. https://spec.graphql.org/

There are hundreds of GraphQL courses and tutorials out there. I would recommend that you study GraphQL before starting with Dgraph. And then go back to studying Dgraph. The concepts are very similar, you will not have difficulty.

@forstmeier

The “primary” endpoint on a Dgraph database seems to be geared towards receiving GraphQL± queries while the /graphql endpoint is designed to receive “regular” GraphQL - is that correct?

Yes, GraphQL+- is the main lang of Dgraph. And /graphql endpoint receives only “pure graphql”.

Cheers.