How xuanmai1812/event_checkin_system works
This is a three-service event ticketing system: organizers create events, attendees register and receive signed QR tickets by email, and staff scan tickets for check-in. Registration publishes ticket-created events so email delivery does not block registration; the worker consumes them, while check-in independently verifies tickets and records admissions. The README documents the Redis Stream, per-service databases, and gateway behavior. Some internal integrations are represented from README statements because their implementation was not excerpted.
Main entry points: registrations.py Registration API · checkin.py Check-in API · consumer.py Stream Consumer · events.py Event API
Components 22
Registration Service
- Registration API
registration-service/app/routers/registrations.py - Event API
registration-service/app/routers/events.py - Registration Data Access
registration-service/app/crud.py - Ticket Signing and QR
registration-service/app/security.py - Ticket Event Publisher
registration-service/app/events.py - Registration Models
registration-service/app/models.py - Registration Database
registration-service/app/database.py
Check-in Service
- Check-in API
checkin-service/app/routers/checkin.py - Ticket Verification
checkin-service/app/security.py - Check-in Data Access
checkin-service/app/crud.py - Check-in Records
checkin-service/app/models.py - Check-in Database
checkin-service/app/database.py
Notification Worker
- Stream Consumer
notification-worker/app/consumer.py - Ticket Email Sender
notification-worker/app/notifier.py - Sent-Email Data Access
notification-worker/app/crud.py - Notification Records
notification-worker/app/models.py - Worker Database
notification-worker/app/database.py
Messaging and Storage
- Redis Stream
- Email Service
Other components
- Attendees
- Gate Staff
- Nginx Gateway
Connections 26
- Attendees → Nginx Gateway: submit requests
- Nginx Gateway → Event API: routes events
- Nginx Gateway → Registration API: routes registration
- Gate Staff → Nginx Gateway: submit scans
- Nginx Gateway → Check-in API: routes check-in
- Event API → Registration Data Access: calls
registration-service/app/routers/events.py - Registration API → Registration Data Access: checks and stores
registration-service/app/routers/registrations.py - Registration API → Ticket Signing and QR: signs and renders
registration-service/app/routers/registrations.py - Registration API → Ticket Event Publisher: publishes ticket
registration-service/app/routers/registrations.py - Registration Data Access → Registration Models: uses models
registration-service/app/crud.py - Registration Models → Registration Database: uses base
registration-service/app/models.py - Registration API → Registration Database: gets session
registration-service/app/routers/registrations.py - Event API → Registration Database: gets session
registration-service/app/routers/events.py - Ticket Event Publisher → Redis Stream: publishes event
- Redis Stream → Stream Consumer: delivers messages
- Stream Consumer → Ticket Email Sender: sends ticket email
notification-worker/app/consumer.py - Stream Consumer → Sent-Email Data Access: checks and records
notification-worker/app/consumer.py - Sent-Email Data Access → Notification Records: uses models
notification-worker/app/crud.py - Notification Records → Worker Database: uses base
notification-worker/app/models.py - Stream Consumer → Worker Database: creates tables and sessions
notification-worker/app/consumer.py - Ticket Email Sender → Email Service: sends email
- Check-in API → Ticket Verification: verifies token
checkin-service/app/routers/checkin.py - Check-in API → Check-in Data Access: records admission
checkin-service/app/routers/checkin.py - Check-in Data Access → Check-in Records: uses models
checkin-service/app/crud.py - Check-in Records → Check-in Database: uses base
checkin-service/app/models.py - Check-in API → Check-in Database: gets session
checkin-service/app/routers/checkin.py