Define the service that needs to stay available.
Name the customer actions or internal processes that matter, such as authentication, order placement or API responses. Set the operating hours, acceptable interruption and performance conditions. A reachable server is only useful if the business transaction can still complete.
List the failure scenarios to address: application process failure, host maintenance, a storage problem or loss of a location. Agree what remains outside the design. Any availability commitment should have a stated measurement boundary and contractual terms.
Make the application ready for multiple instances.
Load balancing can distribute requests across healthy application instances. The health checks need to reflect useful readiness, and the application must handle sessions, background work and shared files correctly. Define what happens to requests already in progress when an instance is removed.
Identify databases, queues and other stateful services. They may need their own replication, failover and consistency approach. Adding web servers alone does not remove a single dependency that every request must use.
Separate the components that fail together.
Ask which resources share a host, storage system, network path or location. Where separation is required, make it an explicit placement rule. Include the capacity needed to serve the workload while part of the environment is unavailable.
Consider DNS, identity services, certificates and external APIs in the same review. Some dependencies need fallback behaviour rather than another identical server. Record who owns each dependency and the operational response if it becomes unavailable.
Prove failover and the return to normal.
Plan controlled tests with an agreed scope, rollback conditions and business approval. Measure customer-visible behaviour as well as infrastructure events. Check alert routing, data consistency and the steps required to return recovered components to service.
High availability and disaster recovery should be designed together. Backups remain relevant for data loss or corruption even when live components are duplicated. Request a proposal that separates architecture, implementation, ongoing management and any service commitments, with evidence required for acceptance.
