Cross-Database Table Selection for MySQL
Capture tables from multiple MySQL databases with a single connector instead of creating a separate connector for each database.
Teams running MySQL can split their data across multiple databases - sometimes for tenancy, sometimes for logical separation, sometimes just historical reasons. Until now, capturing from multiple databases meant creating multiple connectors. That setup worked, but it added configuration overhead and made large environments harder to manage. This update simplifies the workflow without changing how existing connectors behave.
You can now capture tables from multiple MySQL databases using a single connector. Instead of spinning up separate connectors for sales_db, inventory_db, and analytics_db, you can select tables from all of them under one configuration. Artie handles the routing and CDC capture behind the scenes, so your pipelines stay clean while your coverage expands.
Why this matters:
- Reduces connector sprawl across MySQL environments
- Cuts down configuration and long-term maintenance
- Makes it easier to scale CDC coverage as databases multiply
- Simplifies monitoring and observability with fewer moving pieces
- Ideal for teams managing sharded, multi-database, or multi-tenant MySQL setups