Choosing the Right Technology for your API
summary
Compares concrete tradeoffs: Thrift fastest in raw TCP with a very expressive IDL and safe evolution; gRPC requires HTTP/2 and adds bidirectional streaming ideal for Kubernetes-style control planes; REST wins for internet-facing APIs thanks to caching and ubiquity; SSE beats WebSocket for most event use cases unless binary frames or ultra-low overhead are required. Labs use Docker to build clients/servers for Thrift, gRPC, REST, SSE, WebSocket, GraphQL and Kafka+Avro with schema registry.
AI-written summary · about
chapters (5)
- 0:00Start
- 19:25Building a Resource Oriented API with REST
- 26:16Building an RPC API with Apache Thrift
- 31:40Building an Event driven API with SSE
- 46:28Messaging APIs with Apache Kafka, Schema Registry and Apache Avro
related talks
38mAdvanced API Design for Scalable Distributed Systems
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
01h 01mAn Architect's Approach to API Strategies
17mBoost API Performance: gRPC vs REST vs Async
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
42mREST API vs gRPC, Which One Should You Use in Breaking a Monolith
45mREST, gRPC, SignalR and GraphQL for .NET developers
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!