A "change data capture" library for MySQL / MariaDB

Important: Not ready yet – work in progress

Change data capture (CDC) is a nice mechanism for transferring data from one source to another. Imagine a scenario in which you have a service that writes data into a MySQL / MariaDB based database. What if you want to use that data in a different service as well, but in a slightly different format? This is where CDC comes to play. It helps to observe the mutations that happens on the specific records within the database and generates events out of it. An example:

Imagine you have the following user in the users entity:

---------------------
| ID     | Name     |
---------------------
| 1      | André    |
---------------------

Updating that user via UPDATE users SET name = "André König" WHERE ID = 1; would lead to the following change event when using transcripter:

const event = {
    id: 1567,
    schema: "myService"
    domain: "users",
    type: "update",
    payload: {
        before: {
            id: 1,
            name: "André"
        },
        after: {
            id: 1,
            name: "André König"
        }
    }
};

This event could be taken and pushed to, let's say, a message broker which puts it onto a queue. From there, a different service could consume the event and generate a completely different data structure out of it. This is especially handy when you want to enforce CQRS in order to populate a highly optimized read model.

transcripter is a module that helps you to observe a database and consume the change events in order to transfer it to different destinations. The main goals are:

• Easy to use API surface
• Data Consistency - Due to the fact that the binlog won't contain the whole history, the library will create a snapshot before streaming the log
• Resilient – when you start to observe after a certain time period, it will start where it left off
• Handles backpressure
• Output sink agnostic – you can decide where to send the change events

TBD

MIT © André König