31A dependency keeps burning our error budget while their status page stays green. Walk me through your response.▼hard★ EssentialNewUberNetflixPhonePe◆ premiumTheir green page, your red SLO. Separate their true failure rate from the amplification your own client adds, buffer at the boundary, then escalate with a client-side scorecard instead of feelings.Open full answer →
20Checkout calls five downstream services. Design backpressure so overload degrades instead of collapsing.▼hardNewNetflixDatadogUber○ sign inEvery overloaded system dies the same way: queues turn load into latency, latency into timeouts, timeouts into retry storms. Tiered shedding, deadline propagation, and retry budgets are the design.Open full answer →
35Your product calls thirty third-party APIs, each with its own rate limits and quotas. Design the integration layer.▼mediumNewRazorpaySwiggyInfosys◆ premiumVendor limits are a shared budget your own teams will fight over. Broker the capacity, degrade by priority lane, and never let feature code see vendor HTTP semantics.Open full answer →
