How sugrado/telco-crm-microservices works
High-Level Architecture Components
The system consists of the following microservices:
• Account Service
• Basket Service
• Catalog Service
• Config Server
• Customer Service
• Discovery Server
• Gateway Service
• Identity Service
• Invoice Service
• Order Service
• Search Service
Key Architectural Elements
a) Infrastructure Services:
• Config Server: Centralized configuration management
• Discovery Server: Service registry and discovery (Eureka)
• Gateway Service: API Gateway with security controls
b) Core Business Services:
• Identity Service: Authentication and authorization with JWT
• Customer Service: Customer management with individual customer support
• Account Service: Account management
• Catalog Service: Product catalog management
• Order Service: Order processing
• Invoice Service: Invoice generation and management
• Basket Service: Shopping cart functionality
• Search Service: Elasticsearch-based search functionality
Integration Patterns
• Kafka message brokers for event-driven communication
• Redis for caching (used in basket and identity services)
• PostgreSQL databases for persistent storage
• REST API communications between services
• Feign clients for service-to-service communication
┌─ Client Layer
• External Clients/UI
• Gateway Layer
• API Gateway (Security, Routing)
• Service Layer
• Business Services
• Infrastructure Services
• Integration Layer
• Message Brokers
• Service Discovery
• Data Layer
• PostgreSQL
• Redis
• Elasticsearch
Additional Details
Include:
• Service ports and endpoints
• Security boundaries
• Data flow directions
• Event publishing/subscription relationships
• Cache interactions
• Search service indexing flows
Specific Implementation Notes
• How the Gateway Service authenticates with Identity Service
• Event flow from Order Service to Invoice Service
• Demonstrate how Search Service maintains indexes from other services
• Basket Service's interaction with Redis
• How Config Server distributes configurations