hybrid-cloud-outboxes

Sentry uses a transactional outbox pattern for eventually consistent operations. When a model changes, an outbox row is written inside the same database transaction. After the transaction commits, the outbox is drained — firing a signal that triggers side effects such as RPC calls, tombstone propagation, or audit logging.

The most common use case is cross-silo data replication: a model saved in the Region silo produces a RegionOutbox that, when processed, replicates data to the Control silo (or vice versa via ControlOutbox). But the pattern is general — outboxes work for any operation that should happen reliably after a transaction commits, even within a single silo.

There are two outbox types corresponding to the two directions of flow:

在 Sentry 中建立和維護基於寄件箱的最終一致操作的指南。最常用於跨孤島資料複製，但適用於需要最終一致性的任何地方 - 包括單孤島延遲副作用、審核日誌記錄和事件扇出。當要求「新增寄件匣」、「新增寄件匣類別」、「寫入寄件匣訊號接收器」、「偵錯卡住的寄件匣」、「寄件匣未處理」、「資料未複製」、「測試寄件匣」、「移轉資料匣「寄件匣」 「ReplicatedRegionModel」、「ReplicatedControlModel」、「OutboxCategory」、「OutboxScope」或「outbox_runner」。涵蓋模型混合、類別註冊、訊號接收器、測試、回填和調試工作流程。 來源：getsentry/sentry。