Outbox pattern: reliable event publishing from database transactions

the outbox pattern keeps coming up in discussions about reliably publishing events from within a database transaction. the core problem is needing to atomically update a database record and publish an event. doing them separately means potential inconsistencies. the outbox pattern, where you write to an outbox table in the same transaction as your business logic, and then a separate process publishes those events, seems like a solid solution. i'm also exploring change data capture (cdc) tools like debezium as an alternative, which reads from the database transaction log directly. what are the practical trade-offs between implementing an outbox pattern manually versus relying on a cdc tool? specifically around complexity, latency, and operational burden.