⭐ Order Service

order-service is the saga's entry point and the sole owner of an order's overall lifecycle state (PENDING → SUCCESS/CANCELLED). Its topics, port, and schema are on the services-reference.html diagram; the full request path is on saga-flow.html.

OrderController trusts CreateOrderRequest.customerId directly rather than a separately-authenticated identity — api-gateway-service's JWT guard protects the route but doesn't currently inject a verified caller identity for this service to trust instead. A tracked gap, not an oversight.

A GitHub CodeQL scan flagged a real Medium-severity log-injection finding here after deployment (CWE-117): a log line used to interpolate an entire request record, including an unvalidated, unbounded itemCode field straight off the public request body. Fixed by logging fields individually, with itemCode sanitized. The only call site of its kind found across all five modules.