Container service
Generic containerised service you own, on any orchestrator.
- Provider
- default
- Category
- Compute
- Official docs
- https://kubernetes.io/docs/concepts/workloads/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | inherited |
| criticality | enum | low | medium | high | no | medium | inherited |
| instancePerEntity | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | inherited |
| orchestrator | enum | none | kubernetes | ecs | cloud-run | no | none | inherited |
| ownsData | boolean | — | no | true | inherited |
| runtime | string | — | no | — | inherited |
| shardingStrategy | enum | none | consistent-hash | range | lookup | no | none | inherited |
| singleWriter | boolean | — | no | false | inherited |
| stateless | boolean | — | no | true | ▸ 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.
A service that calls a third party synchronously, with no queue or workflow engine attached, has nowhere to park the request when the third party is slow or down. The failure becomes the user's problem instead of a retried job.
- — all of these hold:
- — the node has at least one synchronous outgoing edge to a third-party-api
- — this does not hold:
- — the node has at least one connected edge joining a workflow-engine or queue
Calling a worker synchronously puts the background job on the request path. The caller waits for the slowest part of the fan-out.
- — the node has at least one synchronous outgoing edge to a worker
A stateful service on a consistent hash ring needs something that owns the ring: detect a dead host, pick a replacement, tell everyone. Without a coordination service the ring is edited by hand during the outage.
- — all of these hold:
- — the node's `shardingStrategy` is "consistent-hash"
- — this does not hold:
- — the node has at least one connected edge joining a coordination-service
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: "container-service", component: "container-service" }# yaml-language-server: $schema=../../schema/component.schema.json # The generic app-server implementation: any containerised service you own. # Use a vendor component instead when its specifics matter to a rule. schemaVersion: "1" type: "component" id: "container-service" kind: "app-server" provider: "default" docs: "https://kubernetes.io/docs/concepts/workloads/" defaults: stateless: true properties: orchestrator: type: "enum" values: ["none", "kubernetes", "ecs", "cloud-run"] default: "none"