0Pricing
System Design Basics for Backend Developers · レッスン

キャッシュ無効化パターン

キャッシュデータの鮮度と一貫性を保つための、さまざまなキャッシュ無効化戦略について学びます。

「キャッシュ無効化パターン」はCoddyKit上の無料System Design Basics for Backend Developersレッスンです。 これはレッスン1/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはSystem Design Basics for Backend Developers学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 System Design Basics for Backend Developersコースには全4レッスンが含まれています。

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

What is Cache Invalidation?

Caching helps speed up applications by storing frequently accessed data closer to where it's needed. But what happens when the original data changes?

Cache invalidation is the process of removing or updating cached data when the original source data has changed. It ensures that users always see the most up-to-date information.

The Problem of Stale Data

Imagine you're viewing a product's price on an e-commerce site. If the price changes in the database but your browser (or an intermediate cache) still shows the old price, that's stale data.

Stale data can lead to incorrect information, bad user experiences, or even financial losses. Effective invalidation is key to preventing this.

Time-Based Invalidation (TTL)

The simplest invalidation strategy is Time-To-Live (TTL). Each cached item is given an expiry time. After this time, the item is considered stale and will be removed or refreshed upon the next request.

It's easy to implement but doesn't guarantee immediate freshness if the data changes *before* the TTL expires.

// Example: Setting a cache entry with a TTL
cache.put("user:123", userData, 300); // Cache for 300 seconds

// When requesting "user:123" after 300 seconds,
// the cache will return null or a stale indicator.

TTL: Simple but Limited

Pros of TTL:

  • Easy to implement and manage.
  • Automatically handles removal of old data.
  • Reduces load on the database periodically.

Cons of TTL:

  • Data can be stale for the duration of the TTL.
  • Choosing an optimal TTL can be tricky.
  • Not suitable for data requiring immediate consistency.

Explicit Invalidation: On-Demand

Explicit invalidation means directly removing a cached item when its corresponding source data changes. This ensures immediate freshness.

When an update occurs in the database, the application explicitly tells the cache to delete the affected item(s). The next read request will then fetch the fresh data from the database and re-populate the cache.

// When an item is updated in the database
function updateProduct(productId, newPrice) {
  database.update("products", productId, newPrice);
  cache.delete("product:" + productId); // Explicitly remove from cache
}

Cache-Aside & Explicit Invalidation

This pattern combines the Cache-Aside strategy (where the application manages caching) with explicit invalidation. It's very common.

How it works:

  • Read: Check cache first. If not found, fetch from DB, then store in cache.
  • Write: Update DB first, then explicitly invalidate (delete) the item from the cache.
// Read operation
function getProduct(productId) {
  let product = cache.get("product:" + productId);
  if (product === null) {
    product = database.fetch("products", productId);
    cache.put("product:" + productId, product);
  }
  return product;
}

// Write operation (as seen in previous scene)
// updateProduct(productId, newPrice) {...}

Event-Driven Invalidation (Pub/Sub)

In distributed systems, Event-Driven Invalidation uses a Publish/Subscribe (Pub/Sub) model. When data changes, the service responsible publishes an "update" event to an event bus.

Other services or cache instances that hold a copy of that data subscribe to these events and invalidate their local caches accordingly. This decouples services and ensures consistency across many components.

Versioning for Cache Freshness

Another approach is to use version numbers or timestamps. Each cached item and its corresponding database record can carry a version.

When fetching data, you can compare the cached item's version with the database's version. If the cached version is older, it's stale and needs to be refreshed. This is useful for optimistic concurrency control as well.

// Conceptual check for data freshness
function isCacheStale(cachedItem, dbItem) {
  return cachedItem.version < dbItem.version;
}

// Or using a timestamp
function isCacheStale(cachedItem, dbItem) {
  return cachedItem.lastModified < dbItem.lastModified;
}

Choosing the Right Invalidation

The best invalidation pattern depends on your application's needs:

  • Data Freshness: How critical is it for users to see the absolute latest data?
  • Update Frequency: How often does the data change?
  • System Complexity: How many services share the data?
  • Performance Impact: What's the cost of invalidation vs. the cost of stale data?

Often, a combination of patterns is used.

Invalidation Challenge

You are designing a system for a real-time stock trading platform. Stock prices update very frequently, and showing stale prices could lead to significant financial issues for users.

Which cache invalidation strategy would be most appropriate to ensure users always see the most up-to-date stock prices?

Cache Invalidation Recap

In this lesson, we explored crucial cache invalidation patterns:

  • Time-To-Live (TTL): Simple, time-based expiry.
  • Explicit Invalidation: Direct removal upon data change.
  • Event-Driven (Pub/Sub): For distributed systems to notify changes.
  • Versioning: Comparing data versions/timestamps for freshness.

Choosing the right strategy ensures data consistency and a reliable user experience in your systems.

よくある質問

「キャッシュ無効化パターン」レッスンは無料ですか？

はい。「キャッシュ無効化パターン」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、System Design Basics for Backend Developersコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 System Design Basics for Backend Developersコースには全4レッスンが含まれています。

「キャッシュ無効化パターン」で何を学びますか？

キャッシュデータの鮮度と一貫性を保つための、さまざまなキャッシュ無効化戦略について学びます。 ブラウザで直接実行するハンズオンコードでSystem Design Basics for Backend Developersを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

System Design Basics for Backend Developersを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのSystem Design Basics for Backend Developersは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン1/4です。

「キャッシュ無効化パターン」レッスンにはどのくらい時間がかかりますか？

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

このSystem Design Basics for Backend Developersレッスンでコードを書いて実行できますか？

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

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

  1. キャッシュ無効化パターン
  2. CDN統合とエッジキャッシュ
  3. Redisによる分散キャッシュ
  4. キャッシュの追い出しポリシー
← System Design Basics for Backend Developersに戻る