You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Research some other serialization formats and whether they have implications for content-types / status codes. For example, the usual case that we consider is GraphQL over HTTP with JSON as the serialization format. However, there are other serialization formats in use and this may give us insight as to what the constraints need to be support those in addition to JSON in GraphQL over HTTP.
The text was updated successfully, but these errors were encountered:
It would be awesome to start by researching a list of the possible protocols.
From my point of view I have seen GraphQL with:
BSON (not much difference here)
gRPC (Google, Red Hat)
Thrift (Airbnb folks - backend)
Avro
MessagePack
OData/OpenAPI (Not protocol but graphql wrap those very often)
I would love to add some of the possible constraints that I have seen here as a separate comment over the time assuming that there is interest for those and this is what we looking for here :D
We are using CBOR to support binary fields (with a custom Bytes scalar). CBOR has a media type entry.
Like JSON, CBOR does not need a schema to be parsed so it's basically a drop in replacement (with a lot of additional great stuff like CDDL)
Research some other serialization formats and whether they have implications for content-types / status codes. For example, the usual case that we consider is GraphQL over HTTP with JSON as the serialization format. However, there are other serialization formats in use and this may give us insight as to what the constraints need to be support those in addition to JSON in GraphQL over HTTP.
The text was updated successfully, but these errors were encountered: