Compare
Filament vs Debezium
Side-by-side capabilities and benchmarks.
ROWS PER SECOND
114.8 s
59.8× FASTER
TPC-H, Postgres -> Postgres
WALL TIME
2,597,498
57.1× FASTER
NYC Taxi, Postgres -> Postgres
CPU SECONDS
377
30.9× less
NYC Taxi, Postgres -> Postgres
PEAK MEMORY
2.97 GiB
5.3× less
NYC Taxi, Postgres -> Postgres
Debezium is a change data capture tool. It reads database transaction logs and streams every change as an event, usually into Kafka. It is widely used and widely embedded, and it leaves the initial load, the destination tables, and the surrounding infrastructure to you. Filament is an open-source replication engine that handles the initial load and the ongoing changes in one engine, writes typed tables at the destination, and needs no Kafka to do it.
Verified benchmark comparison
Why Filament
Apache 2.0, open source
Self-hosted in full
Yes. One repository, no paid tier, nothing gated
Adding a new source
A YAML manifest for REST APIs, loaded at runtime with no rebuild. A Go driver for databases and other driver-based sources
Methodology
Configuration as run. Debezium's Taxi figures come from one run of 1 h 49 m. Everything else on this page is a median of three. Filament standalone image, 32 parallel readers, 25,000-row batches. Debezium Server 3.6.1.Final with the JDBC sink, 64 GiB JVM heap, 8 snapshot threads, 8,192-row batches, 10,240-row fetches.
Move data with Filament