Impact of Dependencies on Availability
What you'll learn: How external dependencies and third-party services mathematically compound to reduce your system's overall availability.
The Multiplication Effect
When your system depends on external services, your overall availability becomes the product of all dependencies' availabilities. Each dependency acts as a multiplier that can only reduce (or at best maintain) your system's uptime.
If your service (99.9% available) calls Service A (99.9% available) and Service B (99.9% available) in sequence for every request, your actual availability is:
0.999 × 0.999 × 0.999 = 0.997 (99.7%)
You've lost 0.2% availability just by adding two dependencies!
The Domino Effect in Practice
Think of it like a chain: the chain is only as strong as its weakest link, but every link weakens the whole. Even if all your dependencies seem highly available individually, together they compound into something worse.
With 5 dependencies each at 99.9% ("three nines"):
0.999^5 = 0.995 (99.5%)
With 10 dependencies:
0.999^10 = 0.990 (99.0%)
You've dropped from three nines to two nines simply by having 10 external calls!
Why This Matters for Design
This mathematical reality explains why:
- Microservice architectures must carefully manage inter-service dependencies
- Critical paths should minimize external calls
- Redundancy, caching, and graceful degradation become essential
- You cannot achieve higher availability than your least available critical dependency
Key Takeaway: Every dependency you add multiplies against your availability—a 99.9% service calling 10 other 99.9% services drops to 99% availability, proving that dependencies compound to reduce overall uptime mathematically.