Topic starter
Multi-layer caching (tiered CDN architecture) is a design where a CDN uses multiple levels of caches—instead of just one edge layer—to deliver content more efficiently and reduce load on the origin.
Typical layers in a tiered CDN
1. Edge cache (closest to users)
- Located in many cities worldwide
- First point of contact
- Serves most requests
2. Regional cache / Shield layer
- Fewer, more centralized data centers
- Acts as a second-level cache
- This is where origin shielding fits in
3. Origin server
- Your main backend
- Hit only when content is not cached anywhere
How it works
- User requests a file
- Edge server checks cache
- If hit → return
- If miss → go to regional/shield layer
- Shield layer checks cache
- If hit → return
- If miss → fetch from origin
- Response is cached at both layers
Flow example
User → Edge (miss)
→ Shield (hit)
→ Response (fast, no origin call)
Benefits
1. Higher cache hit ratio
- Even if edge misses, upper layers may have it
2. Massive origin protection
- Origin is hit only as a last resort
3. Reduced latency (overall)
- Fewer long-distance origin fetches
4. Efficient bandwidth usage
- Content reused across regions
5. Handles traffic spikes better
- Prevents “thundering herd” problems
Multi-layer caching is a CDN architecture with multiple cache levels like edge and regional caches. Requests move up the hierarchy on cache misses, improving hit ratio and reducing origin load. Origin shielding is a specific implementation within this model
Posted : 05/04/2026 2:06 pm
