Generic coordination service

Coordination servicecoordination-service

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

Provider: default
Kind: Coordination service
Category: Operations
Official docs: not recorded
Generic?: Vendor-neutral: the kind itself

Properties · 0 set by this component

property	type	values	required	default
consensus	enum	none \| raft \| paxos \| zab	no	none
managed	boolean	—	no	false
nodes	integer	—	no	—
replicated	boolean	—	no	false
role	enum	metadata \| lock \| discovery \| placement \| sharding \| leader-election \| config	yes	—

Rules that apply · 2

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.

Shared dependency without redundancyerror

shared-dependency-without-redundancy

The design requires redundant discovery, but this DNS or coordination service, which everything depends on, runs on a single provider or a single replica. Its failure is the whole system's failure.

— all of these hold:
— the design requirement `availability.discoveryRedundant` is true
— any of these hold:
— the node's `redundantProviders` is false
— the node's `replicated` is false

Stateful engine pinned to a single zoneerror

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"

Use it in a design

nodes:
  - { id: "coordination-service", component: "coordination-service" }

Other Coordination service products · 17

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# The vendor-neutral coordination service: the kind itself, with no product behind it. It sets no
3# defaults and adds no properties, so every required kind property stays required on the node.
4schemaVersion: "1"
5type: "component"
6id: "coordination-service"
7kind: "coordination-service"
8provider: "default"

The same page as markdown, for an agent: /catalogue/components/coordination-service.md