This is the weekly report across five of the leading API specifications, providing a snapshot of these communities that can be used to develop awareness, quantify the scope of, and increase engagement within these communities.
People
Identify one person each week who is doing interesting things within each of these formats.
Description of Use: Automated schema generation and breaking change detection make building and evolving backend GraphQL services a breeze while automated type generation and response mocking help us consume those APIs on the frontend.
Title: Define the need for documentation beyond the current scope of the OAS
Description: The OAS currently focuses on discrete API operations with no implications of what happens before or after this instance of an API call. There are scenarios where there are specific or implied relationships between a group of APIs that can not be expressed in a machine readable format in the OAS and hence can only be communicated out of band by some other means. The draft proposal is to create a machine readable format that would be useful to tool providers, now or in the future, that provides actionable instructions of the intended relationships within a group of APIs.
Title: AuthContext properties are not reset on subsequent calls
Description: It seems the behavior is expected. The auth_context is per-channel, and AuthMetadataProcessor::Process calls per-rpc. For a particular channel, we can have multiple rpc requests. When you update the information in one rpc, it's likely you will see the change in another rpc process request.
Title: What is the meaning of a Media Type Object with no schema defined?
Description: At the moment, we only support JSON Schema for the Schema Object, meaning you can only describe JSON payloads (and to some limited extent XMLs). Had we supported things like XSD (which we may in the future), that would allow you to define schemas (or something similar) for additional media types.
Title: Forward compatibility with must-understand keywords
Description: When submitting JSON Schema as an Internet media type (e.g. application/schema+json), one of the potential problems in JSON Schema is: how does it support forward compatibility?
Title: Enforcing delivery order of payloads - Defer-Stream WG
Description: It was discussed in the 2021-07-01 WG meeting and 2021-12-02 WG meeting and the group agreed that responses like this must be ordered to ensure payload paths do not reference fields that have not been sent yet.
Description: We are excited to announce that the Postman API Platform now supports OpenAPI 3.1 files. OpenAPI 3.1 is the latest version of OpenAPI and was released in February of last year.
Title: Release of graphql-parser and graphql-encoder rewritten in Rust
Description: Nothing in these libraries is specific to Apollo, and can freely be used by other projects which need standards-compliant GraphQL tooling written in Rust.
Title: Calendar invitation for the first gRPC Community Meetup of 2022
Description: In this talk, Ali Hassan, Entrepreneur and engineer in computer science & economics. Founder of WisdomEnigma Inc will present: “gRPC Connection”
Title: What's the role of "JSON Schema in API Design and Development"?
Description: Listen to Ben Hutton @jsonschema specification lead, talking about why it matters and how it's used in APIs and description formats such as @OpenApiSpec and @AsyncAPISpec.
Description: Apollo Federation is a more intuitive option for building distributed GraphQL architectures. It combines multiple GraphQL Schemas into a single data graph.
Description: Ketkee Aryamane covers the fundamentals of gRPC and its key features. Ketkee starts with the basic theory behind RPC and the HTTP/2 protocol, then shows how to build two gRPC services in Java from scratch using protocol buffers, and connects those services with each other using gRPC. She also covers how to generate clients that can invoke those services. If you’re a developer looking for new ways of developing web services, following along with Ketkee as she builds microservices from scratch is a great way to learn new concepts, while also seeing these concepts put to practical use.
This is the weekly report across five of the leading API specifications, providing a snapshot of these communities that can be used to develop awareness, quantify the scope of, and increase engagement within these communities.
People
Identify one person each week who is doing interesting things within each of these formats.
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Adoption
Identify one company or organization that has adopted one of each of these formats (head start available here: OpenAPI, AsyncAPI, JSON Schema)
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
The Beat
Make sure we are covering the beat each week and surfacing relevant information from across the communities.
Any interesting issues? (OpenAPI, AsyncAPI, JSON Schema. GraphQL, gRPC)
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Any interesting discussions? (OpenAPI, AsyncAPI, JSON Schema, GraphQL, gRPC)
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Any interesting news?
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Any interesting tweets?
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Any interesting videos?
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Any interesting tools?
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Any interesting events?
OpenAPI
AsyncAPI
JSON Schema
GraphQL
gRPC
Scope
Quantifying the scope of the communities week by week.
↑ increase from last week
↓ decrease from last week
nc no change from last week
Twitter Followers
Measuring the activity that occurs across Twitter
OpenAPI: 7,730 ↑
AsyncAPI: 3,043 nc
JSON Schema: 884 ↑
GraphQL: 72,050 ↑
gRPC: 15,924 ↑
Github Scope
Measuring the activity occurring across Github
OpenAPI
AsyncAPI
JSON Schema
GraphQL *
gRPC
Stack Overflow Questions
Measuring the activity on Stack Overflow using number of overall questions.
OpenAPI : 9,622 ↑
AsyncAPI: 126 nc
JSON Schema: 32,615 ↑
GraphQL: 44,692 ↑
gRPC: 16,352 ↑