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。