How adamhingoro/micro-restaurants works
Main Components
• API Gateway / Reverse Proxy
• Nginx container (deployment/docker/nginx.conf)
• Frontends
• Admin Panel (microservice-frontend, Svelte + Nginx)
• Restaurant Ordering Front (microservice-restaurant-front, Svelte + Nginx)
• Microservices (each as its own container & K8s Deployment + Service)
1. Users API (authentication, JWT)
2. Customers API (customer data, inter-service validation)
3. Restaurants API (catalog: restaurants, menus, menu items)
4. Orders API (orders & order items, pricing via Restaurants API)
• Databases
• One per service (configurable in deployment/docker-compose-build.yaml or K8s env)
• External Services
• AWS S3 (for image uploads)
• CI/CD & Orchestration
• Travis CI (.travis.yml)
• Docker Build/Run scripts
• Kubernetes (deployment/k8s/*.yaml)
• Okteto CD pipeline (okteto-kubernetes-cd)
Relationships & Data Flows
• Clients (Browser) → HTTP → API Gateway
• Routes “/admin” to Admin Panel
• Routes “/front” to Restaurant Front
• Routes “/api/users/**” to Users API
• Routes “/api/customers/**” to Customers API
• … similarly for /orders, /restaurants
• Frontends → API Gateway → Microservices
• Microservices ↔ Databases (own RDBMS via Sequelize)
• Inter-Service Calls
• Orders API uses Restaurants API (via Axios/objectRequester) for prices
• Customers API verifies with Orders API
• Restaurants API may fetch user info from Users API
• Authentication
• User logs in via Users API → receives JWT
• JWT passed in Authorization headers to all services
• AWS S3
• Any service that needs to upload/fetch images calls AWS SDK
Architectural Patterns & Tech
• Microservices pattern: independent deployable services
• API Gateway pattern: single entry point & routing
• Shared JWT secret for stateless auth across services
• Containerized with Docker, orchestrated by Kubernetes
• Each service uses Express.js + Hapi/Joi for validation + Sequelize for ORM
• Svelte for highly reactive frontends, served via Nginx