It looks like you are implementing the transactional outbox pattern for your DB. In this case, I would create a consumer process that reads messages and routes them to the appropriate workflow in the form of signals. Consider using signalWithStart to crate workflows lazily.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Transactionally triggering Temporal Workflows OR How you can guarantee consistency between database changes and Temporal | 1 | 567 | July 20, 2025 | |
| Postgres Table as Event Source | 4 | 326 | June 17, 2024 | |
| How to handle workflow completion / state change without too many activities? | 7 | 1228 | August 29, 2023 | |
| Use temporal to replace transactional outbox pattern | 5 | 3133 | March 26, 2024 | |
| Possible to store workflow/activity data in another database(own database) | 7 | 2173 | March 31, 2022 |