How rl1m4/kafka works
Project type and purpose
• This is an event-driven, microservice proof-of-concept built with Spring Boot and Spring Kafka.
• Its goal is to demonstrate how a Producer application pushes messages to Kafka, how a Consumer application processes them, and—via the attic examples—how analytics or transactional use cases can be layered on top.
File structure
• Top-level “producer/” and “consumer/” directories each contain a Spring Boot service with Maven wrappers, source code, tests, and application.properties.
• A docker-compose.yml defines the Kafka broker (and Zookeeper).
• Shell scripts (native.sh, save.sh, load.sh, test.sh) automate builds, runs, and tests.
• The attic/analytics and attic/spring-kafka folders are archived examples showing further evolution (analytics pipeline, transactional Kafka usage).
README for additional insights
• The README’s single line confirms intent: “integrate Spring and Apache Kafka.”
Detail is key
• Application.properties to note bootstrap.servers and consumer.group-id.
• That each service runs in its own container (label containers).