Single-region datastore behind a multi-region SLA

errordatastore-single-region

The design promises multi-region availability, but this datastore sits in one region and does not replicate. A region outage takes the system of record with it.

Severity: error
Selects: every node of kind sql-database
Components in scope: 76

What it checks

It looks at every node of kind sql-database, and fires when:

— all of these hold:
— the design requirement `availability.multiRegion` is true
— the node sits inside exactly 1 region group
— the node's `replication` is "none"

Message

Datastore '{{node.id}}' is single-region with no replication, but the design requires multi-region availability.

{{node.id}} style paths are filled in from the node, the edge or the design the finding is about.

Applies to · 76 components

SQL database sql-database

Tripped by · 5

Reference designs whose broken twin names this rule in its header. The gate reads the same header, and fails when a rule no design trips.

linear-syncreference multi-region-webreference netflix-streamingreference paypal-paymentsreference wikipediareference

Source

1# yaml-language-server: $schema=../schema/rule.schema.json
2# The design promises multi-region availability, but this datastore lives in one region
3# with no replication. A region outage takes the system of record with it.
4# Tripped by designs/multi-region-web.broken.yaml.
5schemaVersion: "1"
6type: "rule"
7id: "datastore-single-region"
8severity: "error"
9select:
10  node:
11    kind: "sql-database"
12when:
13  all:
14    - requirement: "availability.multiRegion"
15      equals: true
16    - inGroup:
17        kind: "region"
18        count:
19          eq: 1
20    - prop: "replication"
21      equals: "none"
22message: "Datastore '{{node.id}}' is single-region with no replication, but the design requires multi-region availability."

The same page as markdown, for an agent: /catalogue/rules/datastore-single-region.md