This is Alibaba Canal, a mature, production-grade MySQL binlog change data capture (CDC) system. It simulates a MySQL slave to receive binlog dumps, parses all binlog event types (DDL, DML, GTID, etc.), and delivers the change data to downstream consumers via TCP, Kafka, RocketMQ, RabbitMQ, or Pulsar. It also includes a set of pluggable adapters (via SPI) that can synchronize changes directly to relational databases (RDB), Elasticsearch (6.x/7.x/8.x), HBase, Kudu, Phoenix, ClickHouse, Tablestore, or a simple logger. The system provides high availability through ZooKeeper-based leader election, a web-based admin console (Vue.js + Spring Boot), and Prometheus metrics for monitoring. The architecture is modular with clear separation of concerns: parsing, event sink/ordering, buffered store, metadata management, MQ connectors, and adapter plugins. While the codebase shows its age in places (Netty 3.x usage, some deprecated APIs, duplicated adapter logic across ES versions), it remains a robust and heavily used infrastructure component in many production deployments.