Skip to content

Topic

Database replication

Copying committed changes from one database to another, either by physical log position or as an ordered logical stream of changes that a consumer can resume from.

Current clusters

build1 publisher

At least five ordering questions hide inside one updated_at column

A dev.to walkthrough of PostgreSQL snapshots, LSNs and Oracle SCNs sets out why a row version has no commit coordinate to record when it is written, and what that indirection costs the replication and audit consumers that read it later.

Publishers:dev.to

Reality

Evidence58
Adoption
Insufficient
Hype gap−8
Incentives30
Confidence58