How mamomidev/tmomi-project works
Main Components
a) Service Components:
• tmomi-web (Frontend/API Gateway)
• tmomi-producer (Kafka Producer Service)
• tmomi-consumer (Kafka Consumer Service)
b) Infrastructure Components:
• AWS Services Layer
• Elastic Beanstalk
• Auto Scaling Group
• Application Load Balancer
• Route 53
• AWS MSK (Managed Kafka)
• CloudWatch
c) Data Storage Layer:
• MySQL Database
• Redis (for seat locking)
• Elasticsearch (for search optimization)
d) Monitoring Stack:
• Prometheus
• Grafana
Client Layer
Load Balancer Layer (AWS ALB)
Application Layer
• Web Service
• Producer Service
• Consumer Service
Message Queue Layer (Kafka)
Data Storage Layer
• MySQL
• Redis
• Elasticsearch
Monitoring Layer
Key Relationships to Highlight
• Traffic flow from client through ALB to web service
• Queue-based communication between producer and consumer
• Demonstrate data persistence flows to various storage systems
• Monitoring data collection paths
Implementation Details
Use these specific elements:
• Double lines: High-volume data paths
• Clouds: AWS services
• Rectangles: Application services
Ticket Booking Flow
• Client request → ALB → Web Service
• Web Service → Producer → Kafka → Consumer
• Consumer → MySQL (ticket update)
• Redis (seat locking)
Search Flow
• Client request → ALB → Web Service
• Web Service → Elasticsearch
• Response path back to client
Monitoring Flow
• Services → Prometheus
• Prometheus → Grafana
• CloudWatch integration