A practical deep dive into Kafka offset commit behavior with Spring Boot, demonstrating how applications can lose messages or process them multiple times. Covers three scenarios: single-thread consumption, multi-thread consumption with concurrency, and asynchronous processing via ExecutorService. Shows how graceful shutdown

11m read timeFrom piotrminkowski.com
Post cover image
Table of contents
Source CodeHow It WorksUse Spring Boot with KafkaReceiving MessagesDuplicate Message Processing with Spring KafkaLose Messages with Spring KafkaConclusion

Sort: