Loading content
High availability (HA) denotes architectural and operational practices aimed at minimizing downtime and keeping services continuously accessible. It includes redundancy, failover, replication, monitoring and recovery procedures. Implementing HA requires careful design, automated testing and operational runbooks to handle failures and maintain service levels…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
High availability designs a system to experience as few and as short outages as possible within a defined period.
The discipline grew from the need to keep critical services running through hardware, software, and operational failures. High availability is an architecture and operations practice, not one technology or single originator.
Availability combines redundant components, failure detection, failover, and recovery. When one instance fails, a healthy one serves the workload; shared dependencies can still stop the service. Targets such as an SLA and RTO state how much interruption is acceptable.
Independent resources prevent one failure from ending the service.
A detected failure triggers controlled switching to a functioning resource.
A shared component can remain a central failure point despite many instances.
High availability aligns architecture with business impact and service targets. It adds cost and complexity and does not replace backups or disaster-recovery exercises.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.