# joshivrush/utter-microservices-territory architecture

> Architecture diagram of the GitHub repository joshivrush/utter-microservices-territory, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-01-22). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/joshivrush/utter-microservices-territory
- Repository: https://github.com/joshivrush/utter-microservices-territory

## Overview

##### 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

## Diagram (Mermaid)

```mermaid
graph TB
    subgraph "API Gateway"
        CS["Consumer Service (8400)"]:::microservice
    end

    subgraph "Core Services"
        BS1["Booking Service (8100)"]:::microservice
        BS2["Booking Service (8101)"]:::microservice
        BS3["Booking Service (8102)"]:::microservice
        SS1["Searching Service (8200)"]:::microservice
        SS2["Searching Service (8201)"]:::microservice
        FS["Financial Service (8300)"]:::microservice
    end

    subgraph "Infrastructure Services"
        ESR["Eureka Service Registry (8761)"]:::infra
        RMQ["RabbitMQ (5672)"]:::infra
        ZK["Zipkin (9411)"]:::infra
        DHL["DeadHeat Lock (6379)"]:::infra
    end

    subgraph "Databases"
        PGMASTER["Booking Postgres Master (5432)"]:::database
        PGREPLICA["Booking Postgres Replica (5433)"]:::database
        PGFIN["Financial Postgres (5434)"]:::database
    end

    subgraph "Monitoring Stack"
        ES["Elasticsearch (9200)"]:::monitoring
        LS["Logstash (5044)"]:::monitoring
        KB["Kibana (5601)"]:::monitoring
        FB["Filebeat"]:::monitoring
        SP["Splunk (8000)"]:::monitoring
    end

    %% Service Connections
    CS --> ESR
    BS1 & BS2 & BS3 --> ESR
    SS1 & SS2 --> ESR
    FS --> ESR

    %% API Gateway Routes
    CS --> BS1 & BS2 & BS3
    CS --> SS1 & SS2
    CS --> FS

    %% Database Connections
    BS1 & BS2 & BS3 --> PGMASTER
    PGMASTER -.-> PGREPLICA
    FS --> PGFIN

    %% Message Broker
    BS1 & BS2 & BS3 -.-> RMQ
    FS -.-> RMQ
    CS -.-> RMQ

    %% Distributed Tracing
    BS1 & BS2 & BS3 --> ZK
    SS1 & SS2 --> ZK
    FS --> ZK
    CS --> ZK

    %% Lock Service
    BS1 & BS2 & BS3 --> DHL

    %% Logging Pipeline
    BS1 & BS2 & BS3 & SS1 & SS2 & FS & CS --> FB
    FB --> LS
    LS --> ES
    ES --> KB
    BS1 & BS2 & BS3 & SS1 & SS2 & FS & CS --> SP

    %% Click Events
    click CS "https://github.com/joshivrush/Utter-Microservices-Territory/tree/main/consumer-service"
    click BS1 "https://github.com/joshivrush/Utter-Microservices-Territory/tree/main/booking-service"
    click SS1 "https://github.com/joshivrush/Utter-Microservices-Territory/tree/main/searching-service"
    click FS "https://github.com/joshivrush/Utter-Microservices-Territory/tree/main/financial-service"
    click ESR "https://github.com/joshivrush/Utter-Microservices-Territory/tree/main/netflix-eureka-naming-server"
    click RMQ "https://github.com/joshivrush/Utter-Microservices-Territory/blob/main/docker-compose-rabbitmq.yml"
    click ZK "https://github.com/joshivrush/Utter-Microservices-Territory/blob/main/docker-compose-zipkin-eureka.yml"
    click LS "https://github.com/joshivrush/Utter-Microservices-Territory/blob/main/logstash/pipeline/logstash.conf"
    click FB "https://github.com/joshivrush/Utter-Microservices-Territory/blob/main/filebeat/filebeat.docker.yml"

    %% Styling
    classDef microservice fill:#3498db,stroke:#2980b9,color:white
    classDef infra fill:#2ecc71,stroke:#27ae60,color:white
    classDef database fill:#f1c40f,stroke:#f39c12,color:black
    classDef monitoring fill:#9b59b6,stroke:#8e44ad,color:white

    %% Legend
    subgraph Legend
        L1["Microservice"]:::microservice
        L2["Infrastructure"]:::infra
        L3["Database"]:::database
        L4["Monitoring"]:::monitoring
        L5["--> Sync Communication"]
        L6["-.-> Async Communication"]
    end
```
