Generic event store

Event storeevent-store

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

Provider
default
Category
Messaging
Official docs
not recorded
Generic?
Vendor-neutral: the kind itself
Properties · 0 set by this component
propertytypevaluesrequireddefault
journaledboolean—notrue
managedboolean—nofalse
replicationenumnone | raft | primary-replicanonone
roleenumjournal | sequencernojournal
snapshotIntervalEventsinteger—no—
storageenummmap | rocksdb | databasenodatabase
Rules that apply · 1

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"
Use it in a design
nodes:
  - { id: "event-store", component: "event-store" }
Other Event store products · 4
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# The vendor-neutral event store: 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: "event-store"
kind: "event-store"
provider: "default"

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