How to Build the Status APIs of Your Microservices Ecosystem
summary
Shows how to build service-status APIs by combining simple ping checks with dependency-aware health and reachability probes, enforcing 10 calls/sec rate limits and using 15–30s checks for external services. Describes compiling probe results into a centralized status service that answers a single request for the ecosystem graph, and mentions a published spec, a fragments repo called change, plus middleware and Java/Node libraries used in production.
AI-written summary · about
chapters (11)
- 0:00Status challenge
- 2:35Company context
- 4:06Incident communication issues
- 8:46Service status use cases
- 12:02Initial ping endpoint
- 15:49Ping limitations and king alternatives
- 18:02Rate limiting for dependencies
- 20:57Centralized status service
- 23:09API specs for status
- 25:46Implementation and tools
- 28:19Benefits and future
related talks
30mMeasuring Microservices
26mBuilding Scalable Microservice APIs From The Beginning
51mResponsible Microservices
31mHundreds of Microservices without breaking your APIs
39mObservable microservices
25mMaking microservices a behaviour not a buzzword
50mZen State, and Observability of Your Inner Microservice
40mMeasuring Micro-services