How java-techie-jt/kafka-consumer-example works
This small Spring Boot application consumes JSON Customer events from Kafka topic javatechie-demo and logs each received customer. Startup creates the Spring context; Kafka consumer configuration supplies the broker and deserializers, while Spring Kafka dispatches deserialized events to the annotated listener. The README documents no additional product capabilities, and the supplied source is sufficient to map this single runtime path.
Main entry points: KafkaConsumerConfig.java Consumer configuration · KafkaMessageListener.java Message listener · KafkaConsumerExampleApplication.java Application startup · Customer.java Customer event
Components 10
Application runtime
- Application startup
src/main/java/com/javatechie/KafkaConsumerExampleApplication.java - Customer event
src/main/java/com/javatechie/dto/Customer.java - Application logs
Kafka consumption
- Consumer configuration
src/main/java/com/javatechie/config/KafkaConsumerConfig.java - Consumer properties
src/main/java/com/javatechie/config/KafkaConsumerConfig.java - Consumer factory
src/main/java/com/javatechie/config/KafkaConsumerConfig.java - Listener container factory
src/main/java/com/javatechie/config/KafkaConsumerConfig.java - Message listener
src/main/java/com/javatechie/consumer/KafkaMessageListener.java
Other components
- Event producer
- Kafka broker
Connections 10
- Event producer → Kafka broker: publishes events
- Application startup → Consumer configuration: starts context
- Consumer configuration → Consumer properties: defines properties
- Consumer configuration → Consumer factory: creates factory
- Consumer factory → Consumer properties: reads properties
- Consumer configuration → Listener container factory: creates container factory
- Listener container factory → Consumer factory: sets consumer factory
- Kafka broker → Message listener: delivers topic events
- Message listener → Customer event: accepts deserialized event
- Message listener → Application logs: logs customer