Spring Boot 4 Microservices & REST APIs · Aula

Estratégias de cache para microsserviços

Explore e implemente mecanismos de cache, como o Redis, para melhorar o desempenho dos microsserviços.

Estratégias de cache para microsserviços é uma aula grátis de Spring Boot 4 Microservices & REST APIs no CoddyKit. Esta é a aula 5 de 9. 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 Spring Boot 4 Microservices & REST APIs, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Spring Boot 4 Microservices & REST APIs inclui 9 aulas no total.

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

Why Use Caching?

Imagine your microservice frequently fetches the same data from a database or another slow service. Each request means waiting, consuming resources, and slowing things down.

Performance Boost: Caching stores frequently accessed data closer to your application.
Reduced Load: Less pressure on databases and external services.
Faster Responses: Users experience quicker interactions.

Caching is a powerful technique for optimizing microservice performance.

Understanding Cache Basics

A cache is a temporary storage area that holds copies of data. When your application needs data, it first checks the cache.

Cache Hit: Data is found in the cache, retrieved quickly.
Cache Miss: Data is not in the cache, so it's fetched from the original source (e.g., database) and then stored in the cache for future use.

Think of it like remembering a phone number you dial often!

In-Memory vs. Distributed Cache

There are two main types of caches:

In-Memory Cache: Stored directly within a single application instance. Fast, but data is lost if the instance restarts, and not shared across multiple microservice instances.
Distributed Cache: A separate service (like Redis) that multiple microservice instances can connect to. Data is shared and persistent across instances, crucial for scalable microservices.

For microservices, distributed caching is usually preferred.

Introducing Redis for Caching

Redis (Remote Dictionary Server) is a popular, open-source, in-memory data store. It's often used as a distributed cache due to its speed and versatility.

Key-Value Store: Stores data as simple key-value pairs.
Blazingly Fast: Operations are very quick, often in microseconds.
Versatile: Supports various data structures like strings, hashes, lists, sets, and more.

It's an excellent choice for shared caching in a microservices architecture.

Spring Boot & Redis Setup

To integrate Redis with Spring Boot, you'll need the spring-boot-starter-data-redis dependency.

Add this to your pom.xml (Maven) or build.gradle (Gradle):

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-data-redis</artifactId>
</dependency>

Spring Boot auto-configures Redis if it finds a running instance (e.g., via Docker) or connection properties in application.properties.

Spring's Caching Magic

Spring Boot provides a powerful Cache Abstraction layer. This means you can add caching to your application with simple annotations, without directly interacting with Redis code.

To enable caching in your Spring Boot application, simply add the @EnableCaching annotation to your main application class:

@SpringBootApplication
@EnableCaching
public class MyServiceApplication { ... }

This tells Spring to look for caching annotations on your methods.

Reading from Cache: @Cacheable

The @Cacheable annotation is used on methods whose results you want to cache. When a method annotated with @Cacheable is called:

Spring checks if the result for the given arguments is already in the cache.
If found, the cached value is returned (cache hit).
If not found, the method is executed, its result is stored in the cache, and then returned (cache miss).

Specify a value (cache name) and optionally a key expression.

Live Demo: Caching Concept

This simple Java program demonstrates the core idea behind caching. Notice how the 'database' call count increases only for new IDs, while repeated calls retrieve data instantly from the 'cache'.

import java.util.HashMap;
import java.util.Map;

// A simple in-memory cache
class SimpleProductCache {
    private Map<String, String> cache = new HashMap<>();

    public String get(String key) {
        return cache.get(key);
    }

    public void put(String key, String value) {
        cache.put(key, value);
    }

    public void remove(String key) {
        cache.remove(key);
    }
}

class ProductFetcher {
    private SimpleProductCache productCache;
    private int dbCallCount = 0;

    public ProductFetcher(SimpleProductCache cache) {
        this.productCache = cache;
    }

    public String fetchProductName(String productId) {
        // Try to get from cache first
        String cachedName = productCache.get(productId);
        if (cachedName != null) {
            System.out.println("--> Retrieved '" + productId + "' from cache.");
            return cachedName;
        }

        // If not in cache, simulate database call
        dbCallCount++;
        System.out.println("--> Fetching '" + productId + "' from database (Call #" + dbCallCount + ").");
        try {
            Thread.sleep(100); // Simulate delay
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
        }
        String productName = "Product " + productId + " Name";

        // Store in cache
        productCache.put(productId, productName);
        return productName;
    }
}

public class Main {
    public static void main(String[] args) {
        SimpleProductCache cache = new SimpleProductCache();
        ProductFetcher fetcher = new ProductFetcher(cache);

        System.out.println("--- First requests ---");
        System.out.println(fetcher.fetchProductName("A1"));
        System.out.println(fetcher.fetchProductName("B2"));

        System.out.println("\n--- Repeat requests ---");
        System.out.println(fetcher.fetchProductName("A1")); // Should be from cache
        System.out.println(fetcher.fetchProductName("B2")); // Should be from cache

        System.out.println("\n--- New request ---");
        System.out.println(fetcher.fetchProductName("C3")); // Should be from DB
    }
}

Updating Cache: @CachePut

Sometimes you want to update the cache with the result of a method call, even if the data was already in the cache. This is where @CachePut comes in.

@CachePut(value = "products", key = "#product.id")
public Product updateProduct(Product product) {
  // ... update product in database ...
  return product;
}

Unlike @Cacheable, the method is always executed.
Its result is then placed into the cache.

Use it for methods that modify data and you want the cache to reflect the latest state.

Removing Stale Data: @CacheEvict

When data changes in your database, you need to remove the old, stale data from the cache. The @CacheEvict annotation handles this.

@CacheEvict(value = "products", key = "#id")
public void deleteProduct(String id) {
  // ... delete product from database ...
}

When this method is called, the entry for the specified key in the products cache will be removed.
You can also use allEntries = true to clear the entire cache.

Use it after delete or update operations to ensure data consistency.

Cache Strategy Quiz

You are building a microservice that manages customer data. Which caching strategy would you use for the following scenarios?

Caching for Performance: Recap

Congratulations! You've learned about caching strategies for microservices.

Caching boosts performance and reduces database load.
Distributed caches like Redis are ideal for microservices.
Spring's Cache Abstraction simplifies caching with annotations.
Use @Cacheable for read-heavy operations.
Use @CachePut to update cached entries.
Use @CacheEvict to remove stale cache entries.

Mastering caching helps you build highly scalable and responsive microservices.

Perguntas Frequentes

A aula “Estratégias de cache para microsserviços” é grátis?

Sim — o texto completo de “Estratégias de cache para microsserviços” é 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 Spring Boot 4 Microservices & REST APIs, atualize para CoddyKit PRO. O curso de Spring Boot 4 Microservices & REST APIs inclui 9 aulas no total.

O que vou aprender em “Estratégias de cache para microsserviços”?

Explore e implemente mecanismos de cache, como o Redis, para melhorar o desempenho dos microsserviços. Você pratica Spring Boot 4 Microservices & REST APIs 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 Spring Boot 4 Microservices & REST APIs?

Nenhuma experiência prévia é necessária. Spring Boot 4 Microservices & REST APIs 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 5 de 9.

Quanto tempo leva a aula “Estratégias de cache para microsserviços”?

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 Spring Boot 4 Microservices & REST APIs?

Sim. Cada aula de Spring Boot 4 Microservices & REST APIs 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

← Voltar para Spring Boot 4 Microservices & REST APIs