Service Call Flow

Service Call Flow A sequence diagram generated by Archify. POST /orders propagate W3C context order + outbox transaction 201 Created 201 Created POST /payments propagate W3C context payment + outbox transaction payment result payment result consume each queue / dedup / synthetic result asynchronous, off the response path retry order.created retry payment.completed send success → DB mark Order transaction / HTTP response Payment transaction / HTTP response Asynchronous outbox / independent consumers Client · Sequence participant Client API Gateway · Sequence participant API Gateway Order · Sequence participant Order Payment · Sequence participant Payment Aurora · Sequence participant Aurora SNS →2SQS · Sequence participant SNS →2SQS Consumers · Sequence participant Consumers Legend request return async trace default message

Duplication and causality

  • • Publication and HTTP response ordering can vary
  • • Publish after transaction commit; consumers handle duplicates
  • • W3C context links the asynchronous path