GraphQL, gRPC and REST, Oh My! A Method for Unified API Design

on YouTube ↗18m

" summary

Argues for designing APIs with an interface description layer (properties + actions) rather than HTTP artifacts, then translating that single source into implementation formats. Demonstrates a simple to‑do ALPS descriptor and a CLI tool named unified that emits GraphQL SDL, protobuf RPC stubs and OpenAPI artifacts from the same file. Claims this reduces duplicated governance, keeps URIs/headers/status codes as implementation details, and makes multi‑style ecosystems practical.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 2:07A story of API design & governance
3. 4:17The challenge of HTTP-centric API design
4. 6:34A unified method for API design
5. 9:12Examples/demo
6. 15:10A unified method for API design continued

" related talks

• 24mGraphQL, gRPC, REST, Oh My! - A Method for Unified API DesignMike Amundsen · apidays LIVE Jakarta 2020
• 30mGraphQL, gRPC and REST, Oh My! A Method for Unified API DesignMike Amundsen · GOTOpia Europe 2020
• 01h 00mThe Secrets to Smart, Flexible, Self Describing APIMichael Carducci · Great International Developer Summit 2023
• 51mGraphQL, gRPC or REST? Resolving the API Developer's DilemmaRob Crowley · NDC Sydney 2019
• 59mGraphQL, gRPC or REST? Resolving the API Developer's DilemmaRob Crowley · NDC London 2020
• 59mHandy Tools for Designing Great Web APIsMike Amundsen · NDC Porto 2019
• 24mDesigning the APIs for an Internal Set of ServicesAlberto Leal · RailsConf 2014
• 28mFrom Backend Powerhouses to Web-Friendly APIs: UnlockingMeiyappan Kannappa · Apidays India 2025