DDoS protection strategies in HLD - Architecture Diagram

System Overview - DDoS protection strategies

This system protects a web service from Distributed Denial of Service (DDoS) attacks. It ensures legitimate users can access the service even when attackers try to overwhelm it with fake traffic. Key requirements include filtering malicious traffic, maintaining service availability, and scaling to handle large attack volumes.

Architecture Diagram

Internet

↓

CDN / WAF

↓

Load Balancer

↓

API Gateway

↓

Application Servers

↓

Cache

↓

Database

↓

Traffic Analyzer

Components

User

client

End user accessing the web service

Internet

network

Public network carrying all traffic

CDN / WAF

security_gateway

Filters malicious traffic, blocks known attack patterns, caches static content

Load Balancer

load_balancer

Distributes incoming requests evenly to backend servers

API Gateway

api_gateway

Manages API requests, enforces rate limiting and authentication

Application Servers

service

Processes business logic and user requests

Cache

cache

Stores frequently accessed data to reduce database load

Database

database

Stores persistent data

Traffic Analyzer

monitoring_service

Analyzes traffic patterns to detect anomalies and potential attacks

Message Queue

queue

Buffers alerts and scaling commands asynchronously

Auto Scaling Controller

scaling_service

Automatically adjusts server capacity based on traffic load

Request Flow - 14 Hops

User → Internet

Internet → CDN / WAF

CDN / WAF → Load Balancer

Load Balancer → API Gateway

API Gateway → Application Servers

Application Servers → Cache

Cache → Application Servers

Application Servers → Database

Database → Application Servers

Application Servers → User

CDN / WAF → Traffic Analyzer

Traffic Analyzer → Message Queue

Message Queue → Auto Scaling Controller

Auto Scaling Controller → Application Servers

Failure Scenario

Component Fails:CDN / WAF

Impact:Malicious traffic is no longer filtered, increasing risk of service overload and downtime. Legitimate traffic may also be slowed or blocked incorrectly.

Mitigation:Use multiple CDN/WAF providers with failover. Implement rate limiting and filtering at API Gateway as backup. Monitor traffic closely to detect attacks early.

Architecture Quiz - 3 Questions

Which component first filters out malicious traffic in this architecture?

A CDN / WAF

B Load Balancer

C API Gateway

D Traffic Analyzer

Design Principle

This architecture uses layered defense to protect against DDoS attacks. Early filtering by CDN/WAF reduces load on backend. Rate limiting at API Gateway adds protection. Traffic analysis and auto scaling help detect and respond to attacks dynamically, ensuring availability and scalability.

Practice

1. Which of the following is a primary goal of DDoS protection strategies?

easy

A. Keep the service available during attack

B. Increase the number of incoming requests

C. Slow down legitimate user traffic

D. Disable firewalls to allow all traffic

Solution

1. Step 1: Understand the purpose of DDoS protection

   DDoS protection aims to prevent attacks from making a service unavailable by handling malicious traffic.

2. Step 2: Evaluate each option against this purpose

   Increasing requests or slowing legitimate traffic harms availability. Disabling firewalls reduces security. Only keeping service available matches the goal.

3. Final Answer:

   Keep the service available during attack -> Option A

4. Quick Check:

   DDoS protection = Keep service available [OK]

Hint: DDoS protection means keeping service up, not blocking all traffic [OK]

Common Mistakes:

• Confusing DDoS protection with traffic blocking
• Thinking DDoS protection increases traffic
• Assuming firewalls should be disabled during attacks

2. Which component is commonly used to distribute incoming traffic and help mitigate DDoS attacks?

easy

A. Load balancer

B. Cache server

C. Database server

D. Application server

Solution

1. Step 1: Identify components that manage traffic

   Load balancers distribute incoming requests across multiple servers to prevent overload.

2. Step 2: Match component to DDoS mitigation role

   Load balancers help absorb and spread traffic, reducing attack impact. Other options do not distribute traffic.

3. Final Answer:

   Load balancer -> Option A

4. Quick Check:

   Traffic distribution = Load balancer [OK]

Hint: Load balancers spread traffic to avoid overload [OK]

Common Mistakes:

• Confusing cache or database servers as traffic distributors
• Thinking application servers handle traffic distribution
• Ignoring the role of load balancers in DDoS defense

3. Consider a system using a CDN and a firewall with rate limiting. Which of the following best describes the request flow during a DDoS attack?

medium

A. Requests go directly to the origin server, bypassing CDN and firewall

B. CDN absorbs traffic, firewall filters requests, then origin server processes allowed requests

C. Firewall blocks all requests, CDN caches nothing

D. Origin server handles all requests before CDN and firewall

Solution

1. Step 1: Understand CDN and firewall roles

   CDNs cache content and absorb traffic near users. Firewalls filter malicious requests before reaching origin.

2. Step 2: Trace request flow during attack

   Requests first hit CDN, which reduces load. Firewall then filters suspicious traffic. Only allowed requests reach origin server.

3. Final Answer:

   CDN absorbs traffic, firewall filters requests, then origin server processes allowed requests -> Option B

4. Quick Check:

   Request flow = CDN -> Firewall -> Origin [OK]

Hint: Traffic flows CDN -> Firewall -> Origin server during attack [OK]

Common Mistakes:

• Assuming requests bypass CDN or firewall
• Thinking firewall blocks all requests indiscriminately
• Believing origin server handles all traffic first

4. A system uses IP blacklisting to block attackers, but legitimate users are still affected. What is the likely issue?

medium

A. Firewall is disabled

B. Blacklist is empty, no IPs blocked

C. Blacklist is too broad, blocking shared IPs

D. System does not log blocked IPs

Solution

1. Step 1: Analyze impact of IP blacklisting

   Blacklisting blocks specific IPs. If too broad, it may block IPs shared by many users.

2. Step 2: Identify why legitimate users are affected

   Blocking shared IPs causes collateral damage to good users. Other options do not explain this effect.

3. Final Answer:

   Blacklist is too broad, blocking shared IPs -> Option C

4. Quick Check:

   Legitimate users blocked = Broad blacklist [OK]

Hint: Too broad blacklist blocks good users too [OK]

Common Mistakes:

• Assuming empty blacklist blocks users
• Ignoring shared IP usage in blacklisting
• Thinking firewall status causes this issue

5. You design a DDoS protection system combining CDN, rate limiting, and real-time traffic analysis. Which approach best balances user experience and attack mitigation?

hard

A. Apply strict rate limits globally, blocking many users during spikes

B. Allow all traffic and rely on origin server capacity

C. Disable CDN and rely only on manual IP blocking

D. Use CDN to absorb traffic, apply adaptive rate limits based on analysis, and alert admins on anomalies

Solution

1. Step 1: Evaluate each strategy's impact on users and attack defense

   Strict global limits block many users, hurting experience. Disabling CDN or manual blocking is slow and risky.

2. Step 2: Identify balanced approach

   Using CDN to absorb traffic reduces load. Adaptive rate limits adjust to traffic patterns, minimizing false blocks. Real-time alerts enable quick response.

3. Final Answer:

   Use CDN to absorb traffic, apply adaptive rate limits based on analysis, and alert admins on anomalies -> Option D

4. Quick Check:

   Balanced DDoS defense = CDN + adaptive limits + alerts [OK]

Hint: Combine CDN, adaptive limits, and alerts for best balance [OK]

Common Mistakes:

• Applying strict limits without adaptation
• Ignoring CDN benefits
• Relying only on manual blocking or server capacity