#Change-data-capture
Showing 14 of 14 repositories tagged #change-data-capture, ranked by stars
Open-source data movement for ELT pipelines and AI agents — from APIs, databases & files to warehouses, lakes, and AI applications. Both self-hosted and Cloud.
Incremental engine for long horizon agents 🌟 Star if you like it!
SeaTunnel is a multimodal, high-performance, distributed, massive data integration tool.
🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, by managing your data flows with Estuary. 🌊
A Data Replication Center
Event-Driven Architecture for a microservices-based system with a clean architecture + Domain Driven Design (DDD) + CQRS pattern + Saga pattern + Outbox pattern + CDC.
Example projects and demos around data streaming , stream processing, change data capture, and more.
Frontend & BFF (Backend for frontend) for Olake. This includes the UI code and backend code for storing the configuration of sync and orchestrating it.
Knowledge graph + MCP tool server for LLM agents with hybrid retrieval, live DB sync, Korean FTS, and memory feedback.
slurm-docker-integration provides HPC-Kubernetes integration artifacts
DBConvert Streams: Database IDE, Federated SQL, Real-time CDC & AI assistants via MCP — explore, query, and replicate data across databases and files
A versatile, high-performance Change Data Capture (CDC) engine built in Rust. Streams database changes into downstream systems like Kafka, Redis, NATS and etc, giving you full control over routing, transformation, and delivery.
A high-performance, production-ready PostgreSQL to Any database replication tool using Change Data Capture (CDC) with logical replication.
CDC, radically simplified. One Rust binary replaces Kafka + Debezium + ZooKeeper + Flink. Any source, any target. 300K+ events/sec · <1s latency · ~5 MB RAM. Fewer components = fewer failures + lower cloud bill. Open-source.