Advanced Spring Boot 4: Event-Driven Architecture (Kafka) · 课时

幂等生产者和消费者

进一步了解设计幂等生产者和消费者的重要性,确保即使重新处理消息,状态也能保持一致

第 2 / 4 课11 个步骤

幂等生产者和消费者 是 CoddyKit 上的免费 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课时。 这是第 2 节课,共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 学习路径的一部分,你的进度在网页和 CoddyKit 应用中同步。 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程共包含 4 节课。

本课时的部分内容尚未翻译,以英文显示。

What is Idempotence?

Imagine pressing a light switch. If you press it once, the light turns on. If you press it again, the light stays on – it doesn't get 'more on'. This is idempotence!

An operation is idempotent if performing it multiple times produces the same result as performing it once. It's about the final state, not how many times you tried to get there.

Why Idempotence in Messaging?

In distributed systems like those using Kafka, messages can sometimes be delivered more than once. This can happen due to network issues, consumer crashes, or rebalances.

If your application isn't designed to handle these duplicates, reprocessing the same message multiple times could lead to incorrect data or undesirable side effects.

Kafka's Idempotent Producers

Good news! Kafka provides built-in support for idempotent producers. This means when you send a message, Kafka guarantees that it will be written to the topic log exactly once, even if the producer retries sending it due to transient failures.

This prevents duplicate messages from being stored in Kafka itself.

How Kafka Idempotence Works

Kafka achieves producer idempotence by assigning a unique Producer ID (PID) to each producer session and a monotonically increasing sequence number to each message batch sent by that producer.

Kafka brokers use these IDs and sequence numbers to detect and discard any duplicate message batches before they are written to the log.

Enabling Idempotent Producers

In Spring Boot, enabling an idempotent Kafka producer is straightforward. You just need to set a specific property in your application.properties or application.yml.

  • spring.kafka.producer.properties.enable.idempotence=true

Setting this property also implicitly configures other necessary producer settings, such as acks=all and retries.

Idempotent Producer Example

Try running this simple Spring Boot application. It sends a message to a Kafka topic with idempotence enabled. Notice the configuration comments.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.core.KafkaTemplate;
import org.springframework.boot.CommandLineRunner;
import org.springframework.context.annotation.Bean;
import java.util.UUID;

@SpringBootApplication
public class IdempotentProducerApp {

  public static void main(String[] args) {
    SpringApplication.run(IdempotentProducerApp.class, args);
  }

  @Bean
  public CommandLineRunner runner(
    KafkaTemplate<String, String> kafkaTemplate) {
    return args -> {
      String messageKey = UUID.randomUUID().toString();
      String messageValue = "Hello from Idempotent Producer!";
      System.out.println("Sending message with key: " 
                         + messageKey);
      kafkaTemplate.send("my-idempotent-topic", 
                         messageKey, messageValue)
        .addCallback(
          result -> System.out.println(
            "Message sent successfully!"),
          ex -> System.err.println(
            "Failed to send: " + ex.getMessage())
        );
    };
  }
}
// Add to application.properties:
// spring.kafka.producer.bootstrap-servers=localhost:9092
// spring.kafka.producer.key-serializer=
//   org.apache.kafka.common.serialization.StringSerializer
// spring.kafka.producer.value-serializer=
//   org.apache.kafka.common.serialization.StringSerializer
// spring.kafka.producer.properties.enable.idempotence=true

Idempotent Consumers

While Kafka helps producers avoid sending duplicates to the log, it doesn't guarantee that consumers will process messages exactly once. Consumers might read the same message multiple times.

Therefore, idempotent consumer logic is crucial. This means your application code must ensure that processing a message multiple times has no unintended side effects on your system's state.

Strategies for Idempotent Consumers

Here are common approaches to make your consumers idempotent:

  • Unique ID Tracking: Store a unique identifier (like Kafka's topic-partition-offset or a business ID from the message) in a persistent store. Check this store before processing.
  • State Comparison: Before applying an update, compare the incoming message's data with the current state in your system. Only apply if the state needs changing.
  • Business Idempotence: Design your business operations to be naturally idempotent. For example, 'set user status to X' is idempotent, 'increment user balance by Y' is not.

Consumer Idempotence Example

This Spring Boot example demonstrates a basic idempotent consumer using a set to track processed records. In a real application, this would be a persistent store like a database or Redis.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.kafka.annotation.KafkaListener;
import org.springframework.stereotype.Component;
import org.apache.kafka.clients.consumer.ConsumerRecord;
import java.util.HashSet;
import java.util.Set;

@SpringBootApplication
public class IdempotentConsumerApp {

  public static void main(String[] args) {
    SpringApplication.run(IdempotentConsumerApp.class, args);
  }

  @Component
  public static class MyKafkaListener {
    // In a real app, this would be a persistent store (DB, Redis)
    private final Set<String> processedRecordIds = new HashSet<>();

    @KafkaListener(topics = "my-idempotent-topic", 
                   groupId = "idempotent-group")
    public void listen(ConsumerRecord<String, String> record) {
      // Unique ID for the record (topic-partition-offset)
      String recordId = record.topic() + "-" + record.partition()
                        + "-" + record.offset();

      if (processedRecordIds.contains(recordId)) {
        System.out.println("Duplicate record received (ID: " 
                           + recordId + "). Skipping processing.");
        return;
      }

      // Simulate processing the message
      System.out.println("Processing record ID: " + recordId 
                         + ", Key: " + record.key() 
                         + ", Value: " + record.value());
      // Add to processed set AFTER successful processing
      processedRecordIds.add(recordId);

      // In a real scenario, processing might involve DB updates
      // and 'add' would happen as part of a transaction.
    }
  }
}
// Add to application.properties:
// spring.kafka.consumer.bootstrap-servers=localhost:9092
// spring.kafka.consumer.key-deserializer=
//   org.apache.kafka.common.serialization.StringDeserializer
// spring.kafka.consumer.value-deserializer=
//   org.apache.kafka.common.serialization.StringDeserializer
// spring.kafka.consumer.group-id=idempotent-group
// spring.kafka.consumer.auto-offset-reset=earliest

Quick Check: Idempotence

Test your understanding of idempotent operations in messaging.

Recap & Next Steps

Great job! In this lesson, you've learned about the vital concept of idempotence in event-driven systems.

  • You understand why idempotence is critical for maintaining consistent state when messages might be reprocessed.
  • You saw how Kafka's built-in idempotent producers prevent duplicate messages from entering the topic.
  • You explored strategies for building idempotent consumers, ensuring your application handles duplicate messages gracefully.

Mastering idempotence is a key step towards building robust and reliable Kafka applications!

免费开始

用 AI 导师学习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) — 免费

在浏览器中编写并运行真实代码,获得全天候 AI 导师的即时帮助,并在网页或应用中继续学习。

课程
12
课程
48

常见问题解答

「幂等生产者和消费者」课时是免费的吗?

是的 — 「幂等生产者和消费者」的完整文本可在网页上免费阅读。要进行交互式练习(内置代码编辑器和全天候 AI 导师)并解锁 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程的其余内容,请升级到 CoddyKit PRO。 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程共包含 4 节课。

「幂等生产者和消费者」这节课中我会学到什么?

进一步了解设计幂等生产者和消费者的重要性,确保即使重新处理消息,状态也能保持一致 你通过在浏览器中直接运行的动手代码来练习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka),全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 需要有经验吗?

无需任何先前经验。CoddyKit 上的 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课程适合初学者到高级学习者,你可以从这里开始或从头开始,按照自己的节奏学习。 这是第 2 节课,共 4 节。

「幂等生产者和消费者」课时需要多长时间?

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动,所以你能稳步进步,并在网页和应用中从离开的地方继续。

我能在这节 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课中编写并运行代码吗?

能。每节 Advanced Spring Boot 4: Event-Driven Architecture (Kafka) 课都包含内置代码编辑器,你可以在浏览器中直接编写并运行真实代码,并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. Kafka 性能调优技巧
  2. 幂等生产者和消费者
  3. 将 Spring Boot Kafka 应用部署到云端
  4. 容量规划:分区与副本
← 返回 Advanced Spring Boot 4: Event-Driven Architecture (Kafka)