Description
The architecture diagram in README.md documents /health endpoints for all three microservices (order_service, product_service, user_service), but these endpoints are not implemented in the actual code.
Current Behavior
- Calling
GET /health on any service returns 404 Not Found
- No health check endpoints exist in app.py files
Expected Behavior
Each service should respond to GET /health with:
- Status code: 200 OK
- JSON response indicating service health and database connectivity
Location
user_service/app.py
product_service/app.py
order_service/app.py
Impact
- Cannot use health checks for container orchestration
- Documentation-code inconsistency
- Missing critical production feature
Suggested Solution
Implement /health endpoint in each service that:
- Returns 200 OK if service is healthy
- Checks database connectivity
- Returns appropriate JSON response
Description
The architecture diagram in README.md documents
/healthendpoints for all three microservices (order_service, product_service, user_service), but these endpoints are not implemented in the actual code.Current Behavior
GET /healthon any service returns 404 Not FoundExpected Behavior
Each service should respond to
GET /healthwith:Location
user_service/app.pyproduct_service/app.pyorder_service/app.pyImpact
Suggested Solution
Implement
/healthendpoint in each service that: