Orders

v3.4.0·Commerce·team-commercereleased orders/v3.4.0

Owns the Order aggregate. Accepts order placement over HTTP, emits lifecycle events, and consumes payment settlement to close orders out.

At a glance

This service's own neighbourhood: the channels it publishes and consumes, its data products, and who is on the other end. Click a node to trace its connections; double-click a neighbour to open it.

ServiceChannelData productClientsHTTP operationsNo consumer yet

Artifacts

OpenAPI

API Contract

Synchronous order placement and lookup API.

v3.2.0gatedraw

AsyncAPI

Events

Events emitted and consumed by the Order aggregate.

v3.0.0gatedraw

ODCS

Order events history

Append-only historical record of the order lifecycle events.

v1.3.0gatedraw

Gherkin

Placing an order

Acceptance criteria for order placement and guaranteed event publication.

v2.3.0gatedraw

Drive an implementation

These specs are packaged for consumption. An implementation proves it satisfies them; it never redefines them.

Pin the released surface in a contracts.lock at the implementation repo's root and fetch it read-only:

# contract pin - version is the specs release tag, sha its commit
version: orders/v3.4.0
sha: 49645b76b21fd0363cf5bba0fa387215f17e9283

The full loop, covering fetch, strict binding, verification and staying converged via Renovate, is on Drive an implementation.

Commands

• POSTplaceOrder/orders

Queries

• GETgetOrder/orders/{order_id}

Produces

• orders.placed.v2consumed by Payments
• orders.cancelled.v2no consumer in the specs

Consumes

• payments.settled.v2produced by Payments

Data products

• Order events history