How poridhioss/e-commerce-microservices works
Project Type and Purpose
• This is a full-blown microservices-based e-commerce backend. It consists of four loosely coupled Python FastAPI services—user, product, inventory, and order—plus an NGINX API gateway and per-service databases. Its goal is to enable user management, product CRUD with automatic inventory creation, and order processing (including inventory reservation).
File Structure Insights
• Top-level orchestrator: docker-compose.yml
• “nginx/”: API gateway configuration and Dockerfile
• Four service folders, each with its own Dockerfile, .env, docker-compose.yml, requirements.txt, and a FastAPI app under app/ with subfolders:
• api/routes (HTTP endpoints)
• core (config, logging, security)
• db (Postgres or MongoDB client wrappers)
• models and services (business logic)
• Each service persists to its own database (PostgreSQL for user & inventory, MongoDB for product & order).
Key Architecture Details from README
• All services are spun up via root docker-compose up.
• Client commands hit endpoints under /api/v1/**.