Menu
The following is true:
Javascript == Typescript
Typescript != Javascript
Can the same be said for Dgraph's GraphQL+?
GraphQL == GraphQL+
GraphQL+ != GraphQL
The reason for asking, I understand that GraphQL is not sufficient for Dgraph's goals. But does it process GraphQL if needed?
874
There are three types of operations that GraphQL models: query – a read‐only fetch. mutation – a write followed by a fetch. subscription – a long‐lived request that fetches data in response to source events.
The fields in our GraphQL query (i.e. book, authors, name) specify which edges should be followed in the application data graph to get our desired result. This is where GraphQL gets its name: GraphQL is a query language that traverses your data graph to produce a query result tree.
The conclusion to all of this is a simple statement – no, GraphQL is not made obsolete by HTTP/2.
To add to Sergio's answer, GraphQL+- is not fully compatible with GraphQL. We liked GraphQL and used that as a basis for a new graph query language.
However, I think we would likely look at how big of a gap is between GraphQL+- and GraphQL, and if can be bridged, we would (probably close to or after v1.0).
80
The first paragraph on their landing page reads:
We’ve modified the language to better support graph operations, adding and removing features
And also this
GraphQL+- is a work in progress. We’re adding more features and we might further simplify existing ones.
This means that these languages are incompatible. Similar, yes, but each have unique features.
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
