结合 Redis 与 CDN

Welcome! In this lesson, we'll learn how to combine two powerful caching tools: Redis and Content Delivery Networks (CDNs). This approach is called hybrid caching.

By combining them, we leverage their unique strengths to create a highly performant and scalable system. It's like having specialized tools for different jobs!

Redis is an in-memory data store, perfect for caching dynamic, frequently changing data that your application generates or retrieves from a database.

• User Sessions: Storing login tokens.
• Personalized Feeds: Caching a user's unique content.
• Database Query Results: Storing results of expensive queries.

It sits close to your application, providing lightning-fast access to this data.

A Content Delivery Network (CDN) specializes in distributing static assets globally. Think of files that don't change often.

• Images: Product photos, profile pictures.
• Videos: Streaming content.
• Static Files: CSS, JavaScript, fonts.

CDNs cache these assets at 'edge locations' closer to users, reducing latency and offloading your main servers.

When combined, Redis handles the dynamic, application-specific data, while the CDN takes care of static content. This creates a multi-layered caching strategy.

Here's a simplified flow:

1. User requests a page.
2. CDN serves static assets (images, CSS, JS).
3. Application requests dynamic data (user profile, product list).
4. Application checks Redis cache.
5. If not in Redis, application queries database and stores data in Redis.

Let's consider a user's profile page. It has both dynamic and static elements:

• Dynamic Data (Redis): User's name, email, last login, preferences. This data changes frequently and is specific to each user.
• Static Assets (CDN): User's profile picture, background images, the site's logo, CSS stylesheets. These files are typically uploaded once and don't change often.

This page is a perfect candidate for hybrid caching!

Your application code interacts with Redis to store and retrieve dynamic data. For example, caching a user's name:

When a user's profile is loaded, the application first checks Redis. If found, it's served instantly. If not, it fetches from the database, then stores in Redis for future requests.

SET user:123:name "Alice" EX 3600

GET user:123:name

For static assets like a profile picture, you'd configure your CDN to pull these files from your origin server (where they are stored, e.g., an S3 bucket or your web server).

Instead of linking directly to your server, you'd use a CDN URL:

<img src="https://cdn.example.com/images/profile_alice.jpg">

The CDN caches this image at edge locations, serving it quickly to users worldwide.

Imagine a user in London visiting your profile page hosted in New York:

1. Browser asks CDN for profile_alice.jpg. CDN (e.g., in London) serves it directly from its cache.
2. Browser asks your App for user data. App (in New York) queries Redis (also in New York).
3. Redis serves user:123:name. App gets data instantly.
4. App renders page. Both static and dynamic content load fast!

This hybrid approach offers significant advantages:

• Reduced Latency: Both static and dynamic content load faster by being served from closer caches.
• Lower Origin Load: Your main servers are freed from serving static files and frequent dynamic data lookups.
• Improved Scalability: Each component (CDN, Redis, application) can scale independently.
• Better User Experience: Faster loading times lead to happier users and higher engagement.

Which of the following items would typically be stored in Redis in a hybrid caching architecture, and which would be served by a CDN?

Great job! You've learned how to combine Redis for dynamic, application-level caching and CDNs for static asset delivery.

This powerful hybrid strategy ensures your users get both personalized content and static files delivered with optimal speed and efficiency, significantly boosting performance and scalability. Up next, we'll dive deeper into multi-layer caching strategies!