Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Research other serialization formats #116

Open
sjparsons opened this issue Jul 1, 2020 · 3 comments
Open

Research other serialization formats #116

sjparsons opened this issue Jul 1, 2020 · 3 comments

Comments

@sjparsons
Copy link
Collaborator

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.

@sjparsons sjparsons self-assigned this Jul 1, 2020
@sjparsons sjparsons added this to the July 2020 milestone Jul 1, 2020
@sjparsons sjparsons removed their assignment Jul 1, 2020
@sjparsons sjparsons modified the milestones: July 2020, August 2020 Aug 14, 2020
@sjparsons sjparsons modified the milestones: August 2020, September 2020 Aug 25, 2020
@wtrocki
Copy link

wtrocki commented Aug 27, 2020

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

@Erik1000
Copy link

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)

@valgog
Copy link

valgog commented Jan 3, 2023

Hello, was there any progress on this research?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants