Resilience, Scale and Compliance
Learn to design multi-API systems that handle outages, share rate limits and credits fairly across tenants, protect personal data, and pass an architecture review.
Resilience, Scale and Compliance badgeComplete all 4 lessons to earn it. About 2.8 hours.
0 of 4 lessonsStart course
What you'll be able to do
- Choose fail-open or fail-closed per feature and build fallback chains with circuit breakers and bulkheads
- Split one request's latency budget into per-dependency timeouts that cannot overrun it
- Size worker pools from rate limits and latency, and share one plan fairly across many tenants
- Minimise and redact personal data in requests, logs, caches and audit records
- Write and review an architecture document with SLOs, capacity, failure modes and decision records
This course is one of three skill areas on exam APV-400, APIVerve Certified Architect: Solutions Architecture: 10 of its 30 questions. See the full path
Syllabus
- Fallbacks and graceful degradationStart hereDesign what a multi-API system does when a dependency fails: fail-open or fail-closed per feature, fallback chains, circuit breakers, bulkheads and budgets.
- Queues and fair rate limits for many tenantsLevel bursty load with queues, size workers from rate limits and latency with Little's law, and share one plan fairly across many tenants with backpressure.
- Personal data handling and compliance for APIsSend only the fields each API needs, keep PII out of logs and caches, set retention by data class, and build audit trails a compliance review can rely on.
- Write an architecture reviewWrite and review a design for a multi-API system: SLOs, a dependency inventory with credit costs, capacity math, failure modes, data handling and decisions.