How josebright/refactor-monolith-application-to-microservices works
Main Components Identification
a. Frontend Layer:
• Ionic/Angular web application (udagram-frontend)
• As a single container with internal components for:
• Auth Module
• Feed Module
• Home Module
• API Service Layer
b. Backend Microservices:
• Feed Service (udagram-api-feed)
• User Service (udagram-api-user)
• Reverse Proxy (udagram-reverseproxy)
c. External Services:
• AWS S3 for image storage
• PostgreSQL database
• AWS RDS (if used instead of local PostgreSQL)
[Client Layer]
[Reverse Proxy Layer]
[Microservices Layer]
[External Services Layer]
Component Relationships
• Frontend → Reverse Proxy (HTTP/REST)
• Reverse Proxy → Feed Service & User Service (Internal routing)
• Feed Service → S3 (Image storage)
• Feed Service → PostgreSQL (Feed data)
• User Service → PostgreSQL (User data)
Important Details
a. Infrastructure Elements:
• Docker containers (shown by container boundaries)
• Kubernetes deployments (indicated in deployment files)
• CircleCI pipeline (shown as a CI/CD component)
b. Communication Protocols:
• REST APIs between components
• Database connections
• S3 interactions
Additional Elements
Include:
• Environment variables configuration
• Security boundaries
• Load balancing through reverse proxy
• API versioning (v0 as seen in the code)
Specific Implementation Details
• The separation of user and feed services
• The role of the reverse proxy in routing
• The shared database access pattern
• The authentication flow between services
Technical Specifications
Technical details:
• TypeScript/Node.js backend
• Ionic/Angular frontend
• PostgreSQL database
• AWS S3 storage
• Docker containerization
• Kubernetes orchestration
• CircleCI integration