Caching Strategies: Redis + CDN + Edge Computing · 강의

무효화를 위한 Redis Pub/Sub

여러 애플리케이션 인스턴스에서 실시간으로 캐시를 무효화하기 위해 Redis Publish/Subscribe를 사용하는 방법을 살펴봅니다.

레슨 3/412개 단계

무효화를 위한 Redis Pub/Sub은(는) CoddyKit의 무료 Caching Strategies: Redis + CDN + Edge Computing 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Caching Strategies: Redis + CDN + Edge Computing 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Caching Strategies: Redis + CDN + Edge Computing 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Real-time Cache Updates

Imagine you have multiple copies of your application running, all using a local cache. When data changes in the database, how do you tell all these application instances to update their caches immediately?

Redis Publish/Subscribe (Pub/Sub) is a powerful messaging pattern that allows you to send real-time notifications to multiple clients, making it perfect for distributed cache invalidation.

Beyond Time-To-Live (TTL)

While Time-To-Live (TTL) is great for automatically expiring old data, it doesn't guarantee instant freshness. If critical data changes, you don't want to wait for the TTL to expire.

Pub/Sub provides a way to force immediate invalidation. When data is updated in your primary data store (like a database), one application instance can broadcast a message, and all other instances listening will receive it and invalidate their specific cache entries.

The Publisher Role

In the Pub/Sub model, a Publisher is an entity (like one of your application instances) that sends messages to a specific channel.

When a significant data change occurs (e.g., a product's price is updated in the database), the application instance that made the change acts as a publisher.
It doesn't care who receives the message, only that it's sent to the designated channel.

The Subscriber Role

A Subscriber is an entity (another application instance) that listens for messages on one or more specific channels.

All other application instances would be subscribers to the 'cache-invalidation' channel.
When a message arrives on a channel they're subscribed to, they receive it and can then react, for example, by removing the corresponding item from their local cache.

Redis Pub/Sub Commands

Redis provides two main commands for Pub/Sub:

PUBLISH channel message: Sends message to the specified channel. All subscribers to that channel will receive it.
SUBSCRIBE channel [channel ...]: This client subscribes to one or more channels. Once subscribed, it will continuously listen for messages.

Remember, Pub/Sub messages are fire-and-forget; Redis doesn't store them.

Publishing a Cache Invalidation

Here's how an application instance can publish an invalidation message using Java and the Jedis client. This example sends a message to invalidate a specific product.

import redis.clients.jedis.Jedis;

public class CachePublisher {
  public static void main(String[] args) {
    // Connect to Redis (default localhost:6379)
    Jedis jedis = new Jedis("localhost", 6379);

    String channel = "product-updates";
    String message = "invalidate:product:456"; // Key to invalidate

    // Publish the message
    jedis.publish(channel, message);
    System.out.println("Published: '" + message + "' to channel '" + channel + "'");

    // Close the connection
    jedis.close();
  }
}

Setting Up a Cache Subscriber

Subscribers use a special listener class to handle incoming messages. The onMessage method is where your invalidation logic goes.

Note: The jedis.subscribe() call is blocking and keeps the connection open to listen. In a real app, this runs in a dedicated thread.

import redis.clients.jedis.Jedis;
import redis.clients.jedis.JedisPubSub;

public class CacheSubscriberSetup {
  public static void main(String[] args) {
    System.out.println("Preparing Redis Pub/Sub subscriber...");

    // Define your listener logic
    JedisPubSub listener = new JedisPubSub() {
      @Override
      public void onMessage(String channel, String message) {
        System.out.println("Received: '" + message + "' on channel '" + channel + "'");
        // Here, you would implement your cache invalidation logic
        // e.g., myLocalCache.remove(message.split(":")[1]);
      }

      @Override
      public void onSubscribe(String channel, int subscribedChannels) {
        System.out.println("Successfully subscribed to: " + channel);
      }
      // Other methods like onUnsubscribe, onPMessage, etc., can be overridden
    };

    // In a real application, you'd run:
    // try (Jedis jedis = new Jedis("localhost", 6379)) {
    //   jedis.subscribe(listener, "product-updates"); // This blocks!
    // }
    System.out.println("Subscriber listener defined. To truly listen, run a blocking subscribe call.");
    System.out.println("This runnable example exits to demonstrate setup.");
  }
}

End-to-End Invalidation Flow

Let's see the full picture:

App A updates a product in the database.
App A publishes an invalidation message ('invalidate:product:456') to the 'product-updates' channel in Redis.
Redis receives the message and broadcasts it to all clients subscribed to 'product-updates'.
App B, App C (and App A itself if subscribed) receive the message.
Each app's subscriber logic removes 'product:456' from its local cache, ensuring fresh data on next request.

Designing Invalidation Messages

What should you include in your invalidation message?

Specific Key: 'invalidate:user:123' is ideal for precise invalidation.
Category: 'invalidate:all:products' for broader invalidation (use with caution).
Timestamp/Version: Can help subscribers decide if their cached data is older than the update.

Keep messages concise. Subscribers should have enough info to know what to invalidate.

Pros and Cons of Pub/Sub

Benefits:

Real-time: Immediate cache updates across instances.
Decoupled: Publishers don't need to know about subscribers.
Scalable: Redis handles message distribution efficiently.

Considerations:

No Persistence: If a subscriber is offline, it misses messages.
At-Most-Once: Redis Pub/Sub doesn't guarantee delivery. For critical systems, consider other messaging patterns or a combination.

Pub/Sub Invalidation Quiz

You've learned how Redis Pub/Sub helps with real-time cache invalidation. Let's test your understanding!

인터랙티브 레슨에서 답해보세요

Pub/Sub for Fresh Data

Great job! You've explored how Redis Publish/Subscribe is a vital tool for maintaining data freshness in distributed caching environments.

Pub/Sub allows real-time broadcasting of invalidation messages.
Publishers send messages, and subscribers listen to channels.
This pattern enables immediate cache updates across all application instances when data changes, improving consistency and user experience.
While powerful, remember its 'fire-and-forget' nature and consider persistence needs for critical systems.

무료로 시작

AI 튜터와 함께 Caching Strategies: Redis + CDN + Edge Computing을(를) 배우세요 — 무료

브라우저에서 실제 코드를 작성하고 실행하며, 24/7 AI 튜터로부터 즉각적인 도움을 받고, 웹이나 앱에서 중단한 부분부터 계속 학습하세요.

코스: 12
레슨: 48

무료로 학습 시작 전체 코스 보기

자주 묻는 질문

“무효화를 위한 Redis Pub/Sub” 강의는 무료인가요?

네 — “무효화를 위한 Redis Pub/Sub” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Caching Strategies: Redis + CDN + Edge Computing 강의 전체를 잠금 해제할 수 있습니다. Caching Strategies: Redis + CDN + Edge Computing 강의에는 총 4개의 강의가 포함되어 있습니다.

“무효화를 위한 Redis Pub/Sub”에서 뭘 배우나요?

여러 애플리케이션 인스턴스에서 실시간으로 캐시를 무효화하기 위해 Redis Publish/Subscribe를 사용하는 방법을 살펴봅니다. 브라우저에서 직접 실행하는 실습 코드로 Caching Strategies: Redis + CDN + Edge Computing을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Caching Strategies: Redis + CDN + Edge Computing을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Caching Strategies: Redis + CDN + Edge Computing은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.

“무효화를 위한 Redis Pub/Sub” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Caching Strategies: Redis + CDN + Edge Computing 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Caching Strategies: Redis + CDN + Edge Computing 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Caching Strategies: Redis + CDN + Edge Computing(으)로 돌아가기