Serksa
All Concepts
Performance & Scaling

Redundancy

1

What is it?

<strong>Redundancy</strong> means having backup copies of critical components. If one fails, another takes over immediately, preventing downtime.

2

Think of it like...

The Backup Pilot

Like having a co-pilot ready to take over if the pilot can't fly, redundancy ensures backup systems are ready.

✈️

Main Pilot

Primary system

👨‍✈️

Co-Pilot

Backup ready

🛡️

Safety

No single point of failure

3

Visual Flow

🖥️Server 1

Primary

🖥️Server 2

Backup (ready)

Always Available

No downtime

4

Where you see it

1

Deploy Duplicates

Run multiple copies of servers, databases, etc.

2

Sync Data

Keep backups updated with latest data

3

Monitor Health

Constantly check if primary is working

4

Detect Failure

Notice when primary goes down

5

Automatic Failover

Backup takes over instantly

5

Common Mistake

Wrong

Redundancy is wasteful because backup servers sit idle

Correct

Backups can handle traffic too (load balancing). Even if idle, the cost of downtime (lost revenue, angry users) far exceeds the cost of redundancy.

💡 Real-World Example

Netflix redundancy:

1

Multiple data centers across regions

2

If US-East-1 fails, traffic goes to US-West-2

3

Database has 3 replicas minimum

4

Critical services run on multiple servers

5

You never notice when one server fails