Ensuring High Availability: Functional Separation and Degradation Strategies

“High availability” is a key goal in architecture design; functional separation and degradation are common approaches to achieve it.

Functional Separation

Functional separation distinguishes core business functions (e.g., user login, registration, transaction processing) from non‑core functions (e.g., notifications, log handling). Core functions must remain operational even if non‑core services fail.

Logical separation involves creating independent modules with minimal coupling, communicating via interfaces. Physical separation further isolates resources such as application servers, databases, and caches to prevent non‑core workloads from degrading core performance.

Functional Degradation

When traffic surges or a service becomes unavailable, non‑essential features can be degraded to preserve core functionality. Examples include serving a pre‑rendered static page instead of a dynamic one, or bypassing a third‑party logistics service.

Degradation can be manual —configured via a configuration center with toggle switches—or automatic , where the system detects latency thresholds and switches to a fallback automatically.