Generic matching engine
Matching enginematching-engine
Vendor-neutral matching engine. Use when the real product is not in the catalogue; every rule for this kind still applies.
- Provider
- default
- Kind
- Matching engine
- Category
- Compute
- Official docs
- not recorded
- Generic?
- Vendor-neutral: the kind itself
| 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 |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-engine-pinned-to-single-zone
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.
- — 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
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.
- — 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
nodes:
- { id: "matching-engine", component: "matching-engine" }# 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"