Which of the following best describes the concept of availability in a distributed system?
Think about what it means for a system to be ready and usable at any time.
Availability means the system is up and ready to serve requests whenever users need it. It focuses on uptime and accessibility, not speed or security.
You are designing a web service that must be highly available. Which architectural choice most directly improves availability?
Consider how to avoid a single point of failure.
Multiple servers with a load balancer and health checks ensure if one server fails, others can serve requests, improving availability.
Your service experiences sudden spikes in traffic. Which scaling strategy best maintains availability during these spikes?
Think about adding capacity quickly and flexibly.
Horizontal scaling adds more servers as needed, distributing load and maintaining availability during traffic spikes.
In the context of the CAP theorem, which statement correctly describes the tradeoff between consistency and availability?
Recall the CAP theorem's core principle about network partitions.
The CAP theorem states that during network partitions, a distributed system can only guarantee either consistency or availability, not both.
You operate a service with a target of 99.99% availability. Your current single server has an average downtime of 1 hour per month. How many identical servers with automatic failover do you need to deploy to meet the availability target?
Assume failures are independent and failover is instant.
Calculate availability per server and use the formula for combined availability with failover.
One server availability = (total time - downtime) / total time = (720 - 1) / 720 ≈ 0.9986 (99.86%). Two servers with failover availability = 1 - (1 - 0.9986)^2 ≈ 0.99999796 (99.9998%), which exceeds 99.99% target.