5 ms·
It's got a better name called a transactional outbox https://microservices.io/patterns/data/transactional-outbox.html https://microservices.io/patterns/data/tra
by tlarkworthy 4y ago
It's got a better name called a transactional outbox https://microservices.io/patterns/data/transactional-outbox.html https://microservices.io/patterns/data/transactional-outbox....
- simonw 4y agoYeah, that's a better name for it - good clear explanation too.
- breischl 4y agoOn a quick read this seems like another name for Change Data Capture. In general the pattern works better if you can integrate it with the database's transaction log, so then you can't accidentally forget to publish something. https://en.wikipedia.org/wiki/Change_data_capture https://en.wikipedia.org/wiki/Change_data_capture
- stickperson 4y agoCDC is slightly different; it depends what type of events you are interested in. This is a pretty good read: https://debezium.io/blog/2020/02/10/event-sourcing-vs-cdc https://debezium.io/blog/2020/02/10/event-sourcing-vs-cdc.
- orthoxerox 4y agoCDC is one of the mechanisms you can use to implement this if the volume of message is high, but the idea is to decouple your business transactions from sending out notifications and do the latter asynchronously.