How pranitrout07/a-simple-application-using-two-microservices works
Main Components
• Modern City Photos Microservice: A backend written in Go that serves city photos on port 3142.
• Mountain Photos Microservice: A backend written in Node.js that serves mountain photos on port 3143.
• The deployment of the client (with environment-specific docker image tags)
• The deployment of the two microservices
• The ingress controller (for production) used to route external traffic.
• External Elements: For production, the Nginx ingress should be clearly shown as the entry point for incoming requests from the outside world.
Relationships and Interactions
• In the development environment, show direct port-forward connections – e.g., client on port 3000, city service on port 3142, and mountain service on port 3143.
• Inside the Kubernetes cluster, indicate network flows between the services if desired.
Architectural Patterns and Design Principles
• Microservices: Emphasize that the backend functionality is split into two independent services.
• Containerization: Highlight that each component is containerized (Dockerfile present in each service) for deployment.
• Environment Separation: Clearly annotate differences between production and development – such as multiple replicas and the use of an ingress controller in production versus direct port forwarding in development.
• Cloud/Kubernetes Orchestration: Use a block to represent the Kubernetes cluster, and note that manifests (in manifest_files) are used to manage resources.
Relevant Technologies
• Frontend: React.js (with Vite, Tailwind, etc.)
• Modern City Photos Microservice: Go (with its module system seen in go.mod)
• Mountain Photos Microservice: Node.js (with package.json, Babel, etc.)
• Deployment & Infrastructure: Docker and Kubernetes (with configuration files in manifest_files and kustomization patches for different environments)
• Networking: Nginx Ingress for production routing.