How fernandobono/example-voting-app works
Main Components
a. Vote Frontend
• A web app written in Python (Flask) under vote/app.py or optionally ASP.NET Core under vote/dotnet.
• Exposes an HTTP endpoint (port 5000) for users to cast votes.
b. Message Queue
• Redis (Linux) or NATS (Windows) container collects VoteCastEvent messages.
• Acts as a pub/sub broker between vote frontend and worker.
c. Worker(s)
• One or more background services consuming messages:
• .NET Core worker (worker/dotnet) or Java worker (worker/src/main/java).
• Reads VoteCastEvent from queue, persists to database.
d. Database
• PostgreSQL (Linux) or TiDB (Windows) container.
• Stores vote records.
e. Result Service
• Node.js web app (result/server.js) or ASP.NET Core SignalR app (result/dotnet).
• Subscribes to changes or polls DB, broadcasts real-time results to browser clients on port 5001 via WebSockets/SignalR.
f. Optional Support Services
• seed-data generator (seed-data folder) for demo vote data.
• healthchecks scripts for container health.
g. Orchestration Layers
• Docker Compose files (docker-compose.yml variants)
• Docker Swarm stack files (docker-stack.yml)
• Kubernetes YAML under k8s-specifications
Relationships & Data Flows
1. User → Vote Frontend (HTTP POST vote)
2. Vote Frontend → Message Queue (publish VoteCastEvent)
3. Worker → subscribes to Queue → Worker processes event → Worker → Database (INSERT vote)
4. Result Service → reads from Database (or subscribes to Worker via queue) → broadcasts updates → Browser Result UI (WebSocket/SignalR)
5. (Optional) seed-data → Message Queue → Worker → Database
Architectural Patterns & Principles
• Event-driven microservices: loose coupling via queue.
• CQRS-style separation: writes handled by vote+worker, reads by result service.
• Polyglot services: Python, .NET, Java, Node.js.
• Containerized deployment: Docker Compose, Swarm, Kubernetes.
• Real-time updates via WebSockets / SignalR.
Call Out Key Technologies & Frameworks
• Vote Frontend: Flask (Python) or ASP.NET Core MVC/Razor Pages
• Queue: Redis Pub/Sub or NATS
• Worker: .NET Core Generic Host or Java (Maven)
• DB: Postgres or TiDB
• Result UI: Node.js + socket.io or ASP.NET Core SignalR
• Orchestration: Docker Compose / Docker Swarm / Kubernetes