Build Real Time Communication Between Services
Event-driven architecture lets your services communicate instantly and reliably. This starter project gives you everything you need to get started.
The Problem
Building event-driven architectures from scratch requires understanding multiple technologies: Kafka, Zookeeper, message serialization, producer/consumer patterns, and Docker orchestration. The learning curve is steep, and misconfiguration can lead to message loss or system instability.
The Solution
This complete working example provides everything you need to get an event-driven architecture running in minutes:
- Infrastructure Setup - Docker Compose configuration for Kafka and Zookeeper
- Python Producer Service - Generates and publishes events to Kafka
- Python Consumer Service - Subscribes to topics and processes events
- Clear Project Structure - Organized for easy understanding and extension
The Benefits
- Save 15-25 hours of research and configuration time
- Working code in minutes instead of days
- Production patterns you can adapt for real applications
- Docker-ready infrastructure included
- Simple to extend with your own business logic
Architecture Overview
Producer (Python) --> Kafka --> Consumer (Python)
|
Zookeeper
The producer periodically sends timestamp events. The consumer listens and logs them. Simple, clear, and ready to expand.
What You Get
- Complete
docker-compose.ymlfor infrastructure - Python producer service with
main.py - Python consumer service with
main.py - Requirements files for dependency management
- Full documentation for running the example
Ready to build your own event-driven system.