←  All terms
A
Hosting & Infrastructure

Resilience

Resilience is a system's ability to withstand failures and keep critical functions available or restore them quickly.

Resilience is a system's ability to withstand failures and keep critical functions available or restore them quickly. A robust setup considers availability, security, scalability, observability, and a tested recovery path. The concept is closely related to Uptime and CDN.

Read more

Uptime

CDN

Monitoring

Backup

FAQ

Resilience

Which typical mistakes undermine resilience?
Typical mistakes are untested backups, single points of failure such as one database server, and missing monitoring. Dependencies on third-party scripts are also overlooked, although they can block pages. A recovery plan that has never been rehearsed is unreliable in a real incident.
How much resilience makes sense for a corporate website?
It depends on the damage an outage causes: an online shop or campaign page demands more than a purely informational site. It helps to define acceptable downtime and data loss up front and derive measures from that. Maximum protection is expensive and rarely needed.
Which measures increase the resilience of a website?
Effective measures include redundancy for critical components, a CDN that keeps serving content under load, automated monitoring with alerts, and backups with tested restoration. Static delivery removes failure points. Every measure costs effort, so the scope should match the consequences of an outage.
How does resilience differ from uptime?
Uptime measures in hindsight how long a system was available, while resilience describes how well it absorbs failures and recovers. High uptime can be luck; resilience is design. It only proves itself during an incident, such as the loss of a single component.