alibaba/canal
阿里巴巴 MySQL binlog 增量订阅&消费组件 observed · 2026-10-07
Health v2 · maintenance only
62/100
- Activity 87
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 5028
- days_rel: 642
- days_push: 82
- n_releases_24m: 1
Adoption not part of the score
29740 stars · 7626 forks observed · 2026-10-07
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
Canal is an Alibaba open-source component that parses MySQL binlog to provide incremental data subscription and consumption. It masquerades as a MySQL slave to receive binlog events and can deliver them to clients or message queues like Kafka and RocketMQ.
Use cases
- stream mysql binlog changes to kafka
- keep a search index in sync with a mysql database
- build a real-time database mirror or backup
- refresh application caches on data changes
- capture database changes for event-driven processing
When to choose
- you need change data capture from MySQL without triggers
- you want to fan out database changes to Kafka/RocketMQ consumers
- you need real-time cache invalidation or index maintenance from MySQL
When to avoid
- your source database is not MySQL or a MySQL-compatible RDS
- you need full initial data sync rather than incremental changes
- you want a managed CDC service rather than self-hosted infrastructure
Facets
service · maturity stable
message-queue streaming etl database monitoring databases big-data self-hosted jvm self-hosted mysql-binlog cdc change-data-capture data-sync kafka rocketmq incremental-subscription data-engineering real-time docker linux
1 source
- readme: https://github.com/alibaba/canal · fetched 2026-10-07 · a6bda2ddaba2
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| alibaba/canal | main | 62 |
For agents
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem