Advanced API Design for Scalable Distributed Systems
summary
Compares REST over HTTP for external gateways and Thrift code generation + binary RPC inside the backend, claims binary Thrift beats JSON for latency, and shows cross‑language stubs generated for Java/Python/Go. Describes asynchronous design using Kafka/rocketmq queues with a callback URL or webhook for external partners, shows retry via queue ack/nack. Implements rate limiting with an annotation example limit=5/60s and prevents double actions via an idempotency key stored in DB checked before processing.
AI-written summary · about
chapters (6)
- 0:00intro
- 0:20preamble
- 2:20rest for http and thrift for rpc
- 15:24design asynchronous api calls with callback
- 27:34design rate limiting your apis
- 31:32design idempotency for apis
related talks
48mChoosing the Right Technology for your API
55mForget about HTTP
43mTUTORIAL: We've "REST"ed long enough -- let's have an API adventure!
27mOptimize Your API with Event-Driven Microservice Architecture.
17mBoost API Performance: gRPC vs REST vs Async
31mRPC Frameworks Overview
59mGraphQL, gRPC or REST? Resolving the API Developer's Dilemma
01h 01mAn Architect's Approach to API Strategies
