Outbox pattern: reliable event publishing from database transactions

we're dealing with a common distributed systems problem: needing to atomically update a database record and publish an event related to that change. the classic approach is the outbox pattern: writing the event to an 'outbox' table within the same database transaction as the business logic update, and then having a separate process pick up and publish those events to kafka or a message queue. i'm also aware of change data capture (cdc) tools like debezium that can essentially turn your database commit log into an event stream. what are the trade-offs between implementing an outbox pattern manually versus relying on a cdc solution for reliable event publishing? is cdc generally preferred for its hands-off nature, or does the outbox pattern offer more control for specific event types? keen to hear practical experiences from both sides.