How sachintha-dev/microservice-local-dev-env works
Main Components
A. Service Layer
• Three identical microservices (service-1, service-2, service-3)
• Each service contains:
• Auth API module
• Database connections (MongoDB & Prisma)
• RabbitMQ integration
• Middleware components
• Utility services
B. Infrastructure Layer
• Traefik (Reverse Proxy/Load Balancer)
• Observability Stack:
• Prometheus (Metrics)
• Grafana (Visualization)
• Loki (Logging)
• Tempo (Tracing)
• OpenTelemetry Collector
• Supporting Services:
• Dozzle (Log Viewer)
• cAdvisor
• Node Exporter
┌─ Client Layer ─────────────────────────────┐
• ┬───────────────────────┘
• ↓
┌─ Gateway Layer ────────────────────────────┐
• [Traefik Reverse Proxy] │
• ┬───────────┬───────────────────┘
• ↓ ↓
┌─ Service Layer ──────────────────────────┐
• ┌─────────┐ ┌─────────┐ ┌─────────┐ │
• Service 1│ │Service 2│ │Service 3│ │
• ┬────┘ └────┬────┘ └────┬────┘ │
• ┼───────────┼───────────┼──────────┘
• ↓ ↓ ↓
┌─ Data Layer ────────────────────────────┐
• [MongoDB] [Prisma] │
• ┘
┌─ Observability Layer ──────────────────────┐
• ┌─────────┐ ┌───────┐ ┌─────┐ ┌────────┐ │
• Prometheus│ │Grafana│ │Loki │ │Tempo │ │
• ┘ └───────┘ └─────┘ └────────┘ │
• ┘
Detailed Component Breakdown
For each microservice, show internal structure:
┌─ Microservice (1/2/3) ─────────────────┐
• ┌─────────┐ ┌──────────┐ ┌──────────┐ │
• Auth API │ │Middleware│ │Utils │ │
• ┘ └──────────┘ └──────────┘ │
• ┌─────────┐ ┌──────────┐ │
• Models │ │Config │ │
• ┘ └──────────┘ │
• ┘
Data Flow Indicators
• → Request flow
• ⇢ Event flow
• ⇢ Monitoring data flow
Additional Elements
• Port numbers for each service
• Environment indicators
• Volume mounts
• Configuration file references