0Pricing
System Design Basics for Backend Developers · Aula

Padrões de invalidação de cache

Explore diferentes estratégias para invalidar dados armazenados em cache e garantir atualização e consistência.

Padrões de invalidação de cache é uma aula grátis de System Design Basics for Backend Developers no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de System Design Basics for Backend Developers, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de System Design Basics for Backend Developers inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

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.

Perguntas Frequentes

A aula “Padrões de invalidação de cache” é grátis?

Sim — o texto completo de “Padrões de invalidação de cache” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de System Design Basics for Backend Developers, atualize para CoddyKit PRO. O curso de System Design Basics for Backend Developers inclui 4 aulas no total.

O que vou aprender em “Padrões de invalidação de cache”?

Explore diferentes estratégias para invalidar dados armazenados em cache e garantir atualização e consistência. Você pratica System Design Basics for Backend Developers com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar System Design Basics for Backend Developers?

Nenhuma experiência prévia é necessária. System Design Basics for Backend Developers no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Padrões de invalidação de cache”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de System Design Basics for Backend Developers?

Sim. Cada aula de System Design Basics for Backend Developers inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Padrões de invalidação de cache
  2. Integração com CDN e cache na borda
  3. Cache distribuído com Redis
  4. Políticas de Remoção de Cache
← Voltar para System Design Basics for Backend Developers