Overview
A proof of concept built to solve a real pain point: orchestrating multiple microservices scattered across different repositories. This project validates an architecture where a central monorepo manages independent services through Git submodules, all orchestrated with Docker.
The Problem
Working with microservices in separate repos creates friction — local orchestration is unreliable, dependency alignment becomes manual, synchronized deploys get complex, and end-to-end testing requires too much effort.
The Solution
- A central monorepo that pulls each microservice as a Git submodule
- Each service has its own Dockerfile and
/pinghealthcheck endpoint - Docker Compose orchestrates all containers with dependency management
- NGINX gateway acts as a single entry point, routing traffic to the correct service
- Healthchecks ensure all services are ready before the gateway starts accepting requests
Architecture
Tech Stack
The infrastructure is built with Docker and Docker Compose for container orchestration. NGINX handles reverse proxy and routing. Each microservice runs on Express.js with its own isolated container. Git submodules keep services independent while allowing unified local development.
Monorepo Microservices PoC
February 2026
backendProof of concept for a microservices architecture using a monorepo with Git submodules, Docker orchestration, NGINX gateway, and automated healthchecks.