GraphQL, gRPC and REST, Oh My! A Method for Unified API Design
summary
Claims that API design should be implementation-agnostic and based on properties and actions rather than URLs and HTTP verbs. Uses ALPS descriptors as the abstract design surface and demonstrates a Node-based translator that emits protos + GraphQL + OpenAPI from the same model. Built utility generates protobuf (proto3), GraphQL SDL, and OpenAPI paths and example payloads, reducing duplicate governance and letting teams swap transport formats without rewriting the domain model.
AI-written summary · about
chapters (7)
- 0:00Intro
- 2:50Overview
- 4:49A story of API design & governance
- 10:05The challenge of HTTP-centric API design
- 15:37A unified method for API design
- 19:30Examples/demo
- 28:07A unified method for API design continued
related talks
18mGraphQL, gRPC and REST, Oh My! A Method for Unified API Design
24mGraphQL, gRPC, REST, Oh My! - A Method for Unified API Design
51mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
01h 00mThe Secrets to Smart, Flexible, Self Describing API
43mComparing API Protocols - One Feature at a Time
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
01h 01mAn Architect's Approach to API Strategies
48mHow to Design APIs: Swagger, gRPC, GraphQL — Which to Choose?