liveBook · Manning

Transaction log

As explained in Microservices Patterns, Second Edition

A time-ordered database record of committed changes made by application transactions.

A database transaction log records committed updates. In transaction-log tailing, a relay reads log entries, converts relevant changes—such as inserted outbox messages—into messages, and publishes them to a message broker. section 8.3.8

Tailing can avoid the cost of frequent database polling and can work with outbox messages in relational databases or messages appended to NoSQL records. Its implementation requires a transaction-log miner. section 8.3.8

Figure 8.18 A service publishes messages inserted into the OUTBOX table by mining the database’s transaction log.
TransactionLogMining

Shows the relay mining the transaction log for outbox messages to publish. section 8.3.8

How Microservices Patterns, Second Edition covers it

How deep it goes
Explains how a log miner converts relevant entries into messages but does not detail miner internals.
Examples
Names Debezium with Kafka and DynamoDB Streams as practical examples.
What you can do after
Apply transaction-log tailing to publish database changes as messages.
How it connects
Connects transaction-log tailing with the transactional outbox, message relays, message brokers, and database polling.

Also explained in

Compare how 7 books explain transaction log →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.