An account changes from 'starter' to 'pro', then back to 'starter'.
A later table query correctly returns 'starter'. It cannot tell you that either committed transition happened.
Current state answers what exists now. Committed history answers which accepted changes produced it, and in what order.
Replication, audit, billing, and event processing can need different parts of that history.
One native database log can support six functions: CDC, logical replication, heterogeneous replication, audit, point-in-time recovery, and REDO and event replay.
Each function needs a different result.
They still share questions about selection, order, delivery, resume, state, progress, and recovery.
Remac's product model governs those functions through the seven guarantees of the Remac Contract.
1
24
A database-to-search path can start with one polling job.
Then come cursor rules, delete handling, retry handling, failure isolation, reconciliation, alerts, and recovery ownership.
The boxes can stay the same while the operating work keeps growing.
22
Every committed transaction leaves behind a record of what changed and in what order. That record exists because the database needs it to preserve its own guarantees.
But once you can process that history reliably, it becomes useful outside the database too.
You can build downstream systems from the same sequence of changes the database itself considers committed.
That’s the layer we’re building at Remac.
For years, I kept solving the same problem in different forms: the database commits, but the message publish or downstream write after it can still fail.
Outboxes, queues, triggers, debezium, etc helped. The retries, cleanup, monitoring, reconciliation, infrastructure, and separate recovery tools remained.
Eventually, I stopped treating them as separate problems.
That led me to build @getremac , a high-performance, database-agnostic transaction log processor. Remac is built to move fast without weakening correctness, progress, or recovery. Those requirements became the Remac Contract.
The vision is simple: make every committed data change immediately useful to every system that must act on it.






