Skip to content

Research other serialization formats #116

Open

Description

@sjparsons

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.

Activity

  1. self-assigned this
    on Jul 1, 2020
  2. added this to the July 2020 milestone on Jul 1, 2020
  3. removed their assignment
    on Jul 1, 2020
  4. wtrocki commented on Aug 27, 2020

    @wtrocki

    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

  5. Erik1000 commented on Feb 27, 2022

    @Erik1000

    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)

  6. valgog commented on Jan 3, 2023

    @valgog

    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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions