How to Design APIs: Swagger, gRPC, GraphQL — Which to Choose?
summary
Compare Swagger (OpenAPI), gRPC, and GraphQL for building APIs in microservice architectures, explaining where each technology fits, how to use them correctly to avoid future pain, and how to evolve an existing API. Covers selection criteria, boundaries of applicability, and practical guidance for maintaining and growing APIs built with these tools.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:49Network API theory
- 6:39REST and OpenAPI
- 15:09OpenAPI pros and cons
- 21:33gRPC fundamentals
- 26:44gRPC advantages
- 30:28GraphQL intro
- 36:44GraphQL pros and cons
- 40:28API survival strategies
- 41:15Protocol Buffers and Vulcan
- 47:13Summary
related talks
50mREST, gRPC, GraphQL, Webhooks: When to Use Each?
01h 00mThe Secrets to Smart, Flexible, Self Describing API
43mComparing API Protocols - One Feature at a Time
01h 01mAn Architect's Approach to API Strategies
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
46mREST, GraphQL, gRPC, Webhooks: when to use each?
30mGraphQL, gRPC and REST, Oh My! A Method for Unified API Design
24mGraphQL, gRPC, REST, Oh My! - A Method for Unified API Design