Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by tlarkworthy on Tuesday April 11, 2023 @01:09PM
(#35528026)
It's got a better name called a transactional outbox https://microservices.io/patterns/data/transactional-outbox....
[ Parent
| on HN ]
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by simonw on Tuesday April 11, 2023 @01:23PM
(#35528209)
Yeah, that's a better name for it - good clear explanation too.
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by breischl on Tuesday April 11, 2023 @10:01PM
(#35534161)
On 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.
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by orthoxerox on Wednesday April 12, 2023 @02:18AM
(#35535671)
CDC 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.
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a...
by stickperson on Monday April 17, 2023 @02:51AM
(#35597509)
CDC 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.