Caching Strategies: Redis + CDN + Edge Computing · レッスン

キャッシュフォールバックとCircuit Breaker

フォールバックを設計し、Circuit Breakerを利用して、キャッシュ障害がオリジンに影響を及ぼさない耐障害性の高いキャッシュを実装します。

「キャッシュフォールバックとCircuit Breaker」はCoddyKit上の無料Caching Strategies: Redis + CDN + Edge Computingレッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはCaching Strategies: Redis + CDN + Edge Computing学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Caching Strategies: Redis + CDN + Edge Computingコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Resilient Caching: An Overview

Caching dramatically improves application performance and scalability. But what if your cache itself fails? A truly robust system needs to handle these failures gracefully.

Resilient caching is about designing your systems to remain stable and responsive even when cache systems encounter issues or become unavailable.

The Problem: Cache Failure

When a cache fails, it can lead to serious problems for your backend services. Without the cache to absorb requests, all traffic might suddenly hit your origin server or database directly.

Cache Stampede: Many requests bypass the cache simultaneously.
Origin Overload: The database or API struggles to handle the sudden surge in traffic.
Cascading Failures: Overloaded origins can fail, leading to more system instability.

Introducing Cache Fallbacks

A cache fallback is a strategy to provide an alternative response when the primary cache is unavailable, returns an error, or even when the origin service fails.

Instead of failing outright or showing an error, your system can serve slightly older data, a default value, or a pre-computed result. This ensures a smoother, more consistent user experience.

Fallback Strategy: Stale-While-Revalidate

The Stale-While-Revalidate HTTP cache control directive is a great example of a fallback. It tells clients (like browsers or CDNs) that they can immediately serve a stale (slightly old) cached response.

Meanwhile, the client or a proxy asynchronously fetches a fresh version in the background. This prevents users from waiting for the revalidation, improving perceived performance.

Cache-Control: max-age=60, stale-while-revalidate=3600

Implementing Cache-Aside Fallback

With the Cache-Aside pattern, your application first checks the cache. If there's a miss, it fetches data from the origin (e.g., database) and then updates the cache.

You can add a fallback in the catch block: if fetching from the origin also fails, provide a default, static, or last-known-good value instead of throwing an error.

public class Main {
  public static String fetchDataWithFallback(String key) {
    try {
      // Simulate attempting to fetch from cache
      String cachedData = null; // Assume cache miss
      if (key.equals("cachedItem")) {
        cachedData = "Cached content for " + key;
      }

      if (cachedData != null) {
        return "Using cache: " + cachedData;
      }

      // Simulate fetching from origin (can fail)
      if (key.equals("failingItem")) {
        throw new RuntimeException("Origin service error!");
      }
      return "From origin: Live content for " + key;

    } catch (Exception e) {
      // Fallback in case of cache miss AND origin failure
      return "Fallback for " + key + " (Error: " + e.getMessage() + ")";
    }
  }

  public static void main(String[] args) {
    System.out.println(fetchDataWithFallback("normalItem"));
    System.out.println(fetchDataWithFallback("cachedItem"));
    System.out.println(fetchDataWithFallback("failingItem"));
  }
}

What are Circuit Breakers?

A circuit breaker pattern prevents an application from repeatedly trying to execute an operation that is likely to fail. It's like an electrical circuit breaker: when a fault is detected, it 'trips' to prevent further damage.

In caching systems, circuit breakers protect the origin server from an onslaught of requests when the cache or the origin itself is struggling, preventing cascading failures.

Circuit Breaker: States & Transitions

A circuit breaker typically operates in three states:

Closed: Operations are allowed. If failures exceed a threshold, it transitions to Open.
Open: Operations are blocked immediately. After a configured timeout, it transitions to Half-Open.
Half-Open: A limited number of test operations are allowed. If successful, it goes back to Closed; otherwise, it returns to Open.

Conceptual Circuit Breaker Logic

Here's a simplified illustration of how a circuit breaker might protect a call to an origin service. Notice how it stops calling the failing service once the circuit is 'tripped'.

public class Main {
  static boolean isOriginHealthy = true; // Simulates origin health
  static boolean circuitBreakerTripped = false;
  static int consecutiveFailures = 0;
  static final int THRESHOLD = 2; // Trip after 2 failures

  public static String fetchDataFromOrigin() {
    if (circuitBreakerTripped) {
      return "Circuit OPEN: Origin call blocked.";
    }
    try {
      if (!isOriginHealthy) { // Simulate origin failing
        throw new RuntimeException("Origin failed!");
      }
      consecutiveFailures = 0; // Reset failures on success
      return "Data from Origin.";
    } catch (RuntimeException e) {
      consecutiveFailures++;
      if (consecutiveFailures >= THRESHOLD) {
        circuitBreakerTripped = true;
        return "Circuit OPEN: Origin failed. Blocking further calls.";
      }
      return "Origin failed, but circuit still closed. " + (THRESHOLD - consecutiveFailures) + " tries left.";
    }
  }

  public static void main(String[] args) {
    System.out.println(fetchDataFromOrigin()); // Success
    isOriginHealthy = false; // Origin becomes unhealthy
    System.out.println(fetchDataFromOrigin()); // Failure 1
    System.out.println(fetchDataFromOrigin()); // Failure 2, trip circuit
    System.out.println(fetchDataFromOrigin()); // Blocked by circuit
  }
}

Combining Fallbacks and Circuit Breakers

For ultimate resilience, you often combine fallbacks and circuit breakers. They serve different but complementary roles:

Circuit breakers prevent hammering a failing service, protecting your backend.
Fallbacks provide a graceful degradation, ensuring users still get some response even when primary data sources are unavailable.

Together, they create a robust defense against system outages and performance degradation.

Check Your Understanding

Consider a scenario where your primary cache server goes down. Many requests then bypass the cache and hit your database directly, causing it to slow down significantly.

Which pattern would primarily prevent the database from being overwhelmed by these direct requests?

Lesson Recap: Resilience

We've learned how to build more resilient caching systems.

Fallbacks provide alternative content when caches or origins fail, maintaining user experience.
Circuit breakers protect your backend services from cascading failures by stopping repeated calls to unhealthy services.

By implementing these patterns, you can significantly enhance the stability and availability of your applications, even under adverse conditions.

よくある質問

「キャッシュフォールバックとCircuit Breaker」レッスンは無料ですか？

はい。「キャッシュフォールバックとCircuit Breaker」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Caching Strategies: Redis + CDN + Edge Computingコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Caching Strategies: Redis + CDN + Edge Computingコースには全4レッスンが含まれています。

「キャッシュフォールバックとCircuit Breaker」で何を学びますか？

フォールバックを設計し、Circuit Breakerを利用して、キャッシュ障害がオリジンに影響を及ぼさない耐障害性の高いキャッシュを実装します。ブラウザで直接実行するハンズオンコードでCaching Strategies: Redis + CDN + Edge Computingを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Caching Strategies: Redis + CDN + Edge Computingを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのCaching Strategies: Redis + CDN + Edge Computingは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/4です。

「キャッシュフォールバックとCircuit Breaker」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このCaching Strategies: Redis + CDN + Edge Computingレッスンでコードを書いて実行できますか？

はい。すべてのCaching Strategies: Redis + CDN + Edge Computingレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Caching Strategies: Redis + CDN + Edge Computingに戻る