| title | component | reviewed | related | |
|---|---|---|---|---|
Outbox with SQL persistence |
SqlPersistence |
2025-03-21 |
|
The outbox feature requires persistence in order to store the messages and enable deduplication.
To keep track of duplicate messages, the SQL persistence implementation of outbox requires the creation of dedicated outbox tables. The names of the outbox tables are generated automatically according to the rules for a given SQL dialect, for example the maximum name length limit.
By default, the endpoint name is used as the table prefix to ensure that message identities for each endpoint are separated from each other.
Warning
Configuring the same table prefix for endpoints sharing the same database will cause message loss for endpoints that are subscribed to the same event.
See scripts used for table creation to learn more: MS SQL Server, Oracle, MySQL and PostgreSQL.
partial: modes
By default, the SQL persistence implementation keeps deduplication records for 7 days and runs the purge every minute.
partial: settings
In scaled-out environments, endpoint instances compete to execute outbox cleanup, which can result in occasional conflicts. There are a few options available to minimize this:
- Run the cleanup on only a single instance.
- Increase the cleanup interval so that, on average, one endpoint instance cleans up as often as a single instance would normally. The cleanup timer isn't strict and over time these will drift and will cause less overlap. For example, for 10 endpoint instances, let cleanup run every 10 minutes instead of every minute.
- Disable cleanup on all instances and run cleanup as a scheduled job in the database. See the dialect-specific scripts for more details: