Skip to content

Data & Event Platform — workers, grains and sagas

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.

Workers

Worker Service Trigger Output events Retry Idempotency key Concurrency
ModelSync EnvelopeRegistryService manual on release of the architecture model TopicRegistered, SchemaVersionPublished fixed ×2 topic + schemaVersion 1 by none
DeprecationSweeper EnvelopeRegistryService schedule 0 2 * * * — none ×1 topic + day 1 by none
BindingReconciler StoreProfileService schedule 0 */6 * * * StoreBindingChanged fixed ×2 storeId + window 2 by Region
RetentionSweeper RetentionResidencyService schedule 0 3 * * * DeletionOrderIssued fixed ×2 ruleId + day 2 by TenantId
OrderDispatcher RetentionResidencyService event RetentionResidencyService.DeletionOrderIssued DeletionOrderCompleted exponential ×5 orderId + ownerService 4 by TenantId
Exporter RetentionResidencyService event RetentionResidencyService.DeletionOrderIssued ExportCompleted exponential ×3 orderId 2 by TenantId
  • ModelSync (EnvelopeRegistryService): Applies the topics, producers, consumers and schema references of the architecture model (the generated catalogs) to the registry at release time and reports drift.
  • DeprecationSweeper (EnvelopeRegistryService): Retires topics whose deprecation window elapsed.
  • BindingReconciler (StoreProfileService): Compares bindings with the observed state from provisioning and flags drift (missing schema, wrong region, key rotation overdue).
  • RetentionSweeper (RetentionResidencyService): Computes expiry per rule and issues purge tasks to owning services (delete, redact or archive) with receipts.
  • OrderDispatcher (RetentionResidencyService): Fans an order out to every owning service as tasks, tracks acknowledgements and marks orders Completed or Overdue.
  • Exporter (RetentionResidencyService): Collects export bundles from owning services into one archive with a manifest in open formats.

Grains (actors)

None modelled

No grains are modelled for this item yet.

Sagas

Saga Service Correlation Starts on Steps Ends on
TenantDeletionSaga RetentionResidencyService orderId RetentionResidencyService.DeletionOrderIssued 5 DeletionOrderCompleted