---
id: "matching-engine"
type: "component"
kind: "matching-engine"
provider: "default"
category: "compute"
url: "https://localhost:3000/catalogue/components/matching-engine"
---

# Generic matching engine

Vendor-neutral matching engine. Use when the real product is not in the catalogue; every rule for this kind still applies.

| | |
|---|---|
| Provider | [default](https://localhost:3000/catalogue?provider=default) |
| Kind | [Matching engine](https://localhost:3000/catalogue/kinds/matching-engine) |
| Category | Compute |
| Official docs | not recorded |
| Generic? | Vendor-neutral: the kind itself |

## Properties

| property | type | values | required | default |
|---|---|---|---|---|
| `algorithm` | enum | `price-time`, `pro-rata` | no | "price-time" |
| `deterministic` | boolean | — | no | true |
| `failover` | enum | `none`, `manual`, `automatic` | no | "none" |
| `managed` | boolean | — | no | false |
| `role` | enum | `primary`, `standby` | no | "primary" |
| `singleThreaded` | boolean | — | no | true |

## Rules that apply · 2

### Stateful engine pinned to a single zone `stateful-engine-pinned-to-single-zone` (error)

- Page: https://localhost:3000/catalogue/rules/stateful-engine-pinned-to-single-zone.md
- Why: A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.
- Applies to: every node of kind matching-engine, coordination-service or event-store
- Message: '{{node.id}}' is pinned to a single availability zone with no failover or replication.

It fires when:

- all of these hold:
  - the node sits inside exactly 1 availability-zone group
  - any of these hold:
    - the node's `failover` is "none"
    - the node's `replicated` is false
    - the node's `replication` is "none"

### Stateful node without zone redundancy `stateful-node-without-zone-redundancy` (error)

- Page: https://localhost:3000/catalogue/rules/stateful-node-without-zone-redundancy.md
- Why: A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- Applies to: every node in category compute
- Message: Stateful node '{{node.id}}' lives in exactly one availability zone. A zone outage takes its state with it.

It fires when:

- all of these hold:
  - the node's `stateless` is false
  - the node sits inside exactly 1 availability-zone group
  - this does not hold:
    - the node sits inside at least one cell group

## Other products of the same kind · 2

- [Amazon GameLift FlexMatch](https://localhost:3000/catalogue/components/aws-gamelift-flexmatch.md) `aws-gamelift-flexmatch` — aws
- [Order-book matcher](https://localhost:3000/catalogue/components/order-book-matcher.md) `order-book-matcher` — default

## Use it in a design

```yaml
nodes:
  - { id: "matching-engine", component: "matching-engine" }
```

## Source (`component` YAML, verbatim)

```yaml
# yaml-language-server: $schema=../../schema/component.schema.json
# The vendor-neutral matching engine: the kind itself, with no product behind it. It sets no
# defaults and adds no properties, so every required kind property stays required on the node.
schemaVersion: "1"
type: "component"
id: "matching-engine"
kind: "matching-engine"
provider: "default"
```

Human page: https://localhost:3000/catalogue/components/matching-engine