MySQL Agent for Gluesync: Features & Compatibility

Index

Core principles

This agent establishes a connection to MySQL via a built-in JDBC driver.

Change data capture

This agent implements the scraping of Bin log’s transaction logs by connecting to your master, slave or MaxScale instances depending on the desired configuration. To scrape the Bin log it connects to MySQL using a socket TCP connection.

Supported version

With this agent, you can target any version of MySQL, whether is Enterprise, Percona, AWS RDS, MaxScale instances or just the Community edition.

This agent’s version supports one master node with single server ID.

Platform supported features

Feature	Support	Notes
Target role	✅	Writes through the built-in JDBC driver with optional TLS, connection pooling and AWS RDS support.
Source role	✅	Scrapes the Binlog via TCP sockets and supports master, replica or MaxScale endpoints.
Snapshots	✅	Fully compatible with Core Hub snapshot tasks for initial loads and re-syncs.
CDC	✅	Continuously consumes Binlog events for near real-time replication.
CDC type	Transaction logs (Binlog)	Implements MySQL’s native binary log streaming protocol.
Bulk load	✅	Supports staging-table Bulk load flows for high-volume mirroring targets.
Source persisted internal cache	✅	This agent supports locally in-agent persistence see Source agent caching layer.
Target persisted internal cache	N/A	Writes are streamed directly to MySQL without additional local caching.
Driver / connector	Built-in JDBC driver	Vendor-certified JDBC driver bundled with Gluesync, MySQL official driver.
Chains	N/A	Not supported.
Truncate operation support (reading)	✅	Source agent can capture and forward TRUNCATE operations to the target.
Truncate operation support (writing)	✅	Supports TRUNCATE-before-snapshot option when configured in Core Hub.

Feature

Support

Notes

Target role

✅

Writes through the built-in JDBC driver with optional TLS, connection pooling and AWS RDS support.

Source role

✅

Scrapes the Binlog via TCP sockets and supports master, replica or MaxScale endpoints.

Snapshots

✅

Fully compatible with Core Hub snapshot tasks for initial loads and re-syncs.

CDC

✅

Continuously consumes Binlog events for near real-time replication.

CDC type

Transaction logs (Binlog)

Implements MySQL’s native binary log streaming protocol.

Bulk load

✅

Supports staging-table Bulk load flows for high-volume mirroring targets.

Source persisted internal cache

✅

This agent supports locally in-agent persistence see Source agent caching layer.

Target persisted internal cache

N/A

Writes are streamed directly to MySQL without additional local caching.

Driver / connector

Built-in JDBC driver

Vendor-certified JDBC driver bundled with Gluesync, MySQL official driver.

Chains

N/A

Not supported.

Truncate operation support (reading)

✅

Source agent can capture and forward TRUNCATE operations to the target.

Truncate operation support (writing)

✅

Supports TRUNCATE-before-snapshot option when configured in Core Hub.

Change data capture

Works with MySQL starting from 5.5 and above, 8.4 included.

Q&A

I am connecting towards an AWS RDS instance, is it supported? Yes, it is. MySQL RDS instances are supported. Remember to enable SSL connection during agent’s setup phase. For AWS Aurora MySQL-compatible instances, you may want to use instead the MariaDB agent as it is the right choice for this scenario.

I have got MySQL running under a managed DBaaS offered from AWS | CGP | Azure | OCI | …, is it supported? Yes, they are. Just make sure you have enabled transaction logs - Bin log - redaction support.

Video Tutorial

Real time data integration between MySQL 8 to Snowflake 9.15