How arivazhagan7b/basic_microservices works
This repository is a minimal microservices example: ten independent Express processes, each exposing a /health endpoint. The only evidenced user-to-result flow is an HTTP caller requesting a service’s health response; no business operations, gateway routing, inter-service calls, or persistence are shown. The service names suggest distinct domains, but their sampled implementations contain only health checks. In particular, the search endpoint reports gateway in its response. Connections below show only the documented-in-code health requests, not a broader product workflow.
Main entry points: gateway/index.js Gateway · auth/index.js Auth · users/index.js Users · inventory/index.js Inventory
Components 11
Connections 10
- HTTP caller → Gateway: requests health
gateway/index.js - HTTP caller → Auth: requests health
auth/index.js - HTTP caller → Users: requests health
users/index.js - HTTP caller → Inventory: requests health
inventory/index.js - HTTP caller → Orders: requests health
orders/index.js - HTTP caller → Payments: requests health
payments/index.js - HTTP caller → Notifications: requests health
notifications/index.js - HTTP caller → Analytics: requests health
analytics/index.js - HTTP caller → Reports: requests health
reports/index.js - HTTP caller → Search: requests health
search/index.js