How joshivrush/utter-microservices-territory works
Main Components
a. Core Microservices (represented as individual containers):
• Booking Service (with multiple instances: 8100, 8101, 8102)
• Searching Service (instances: 8200, 8201)
• Financial Service (8300)
• Consumer Service (8400)
b. Infrastructure Services:
• Netflix Eureka Service Registry (8761)
• RabbitMQ Message Broker (5672, 15672)
• Zipkin Distributed Tracing (9411)
• DeadHeat Lock Service (6379)
c. Data Stores:
• Booking Postgres Master (5432)
• Booking Postgres ReadOnly Replica (5433)
• Financial Postgres (5434)
d. Logging & Monitoring Stack:
• ELK Stack:
• Elasticsearch (9200)
• Logstash (5044)
• Kibana (5601)
• Filebeat
• Splunk (8000)
Component Relationships
• All microservices should connect to Eureka for service discovery
• Service-to-service communication via Feign clients (with Ribbon for load balancing)
• Event-driven communication through RabbitMQ
• Database connections for respective services
• Logging flow: Services → Filebeat → Logstash → Elasticsearch → Kibana
• Distributed tracing: Services → Zipkin
Key Patterns to Highlight
• Circuit Breaker pattern (Hystrix)
• Service Discovery pattern (Eureka)
• Event-Driven Architecture (RabbitMQ)
• Database Replication (Postgres Master-Replica)
• Distributed Tracing (Sleuth & Zipkin)
• API Gateway pattern (Consumer Service)
Additional Details
Annotations for:
• Port numbers for each service
• Load balancing indicators
• Fault tolerance mechanisms
• Security boundaries
• Data flow directions
Critical Aspects to Emphasize
• High availability through service replication
• Data consistency mechanisms (DeadHeat Lock)
• Monitoring and logging pipeline
• Service independence and loose coupling
• Fault tolerance mechanisms