YugabyteDB Agent for Gluesync: Features Overview

Index

Core principles

This agent establishes a connection to YugabyteDB via YugabyteDB’s built-in JDBC smart drivers, leveraging features such as cluster awareness and load balancing.

Change data capture

Gluesync consumes changes from YugabyteDB by implementing the CDC (Change data capture) technique to read transaction logs from YugabyteDB replication slots technology starting from version 2+;

From the books:

Logical decoding is the process of extracting all persistent changes to a database’s tables into a coherent, easy-to-understand format that can be interpreted without detailed knowledge of the database’s internal state. In YugabyteDB, logical decoding is implemented by decoding the contents of the write-ahead log, which describes changes on a storage level, into an application-specific form such as a stream of tuples or SQL statements. In the context of logical replication, a slot represents a stream of changes that can be replayed to a client in the order they were made on the origin server. Each slot streams a sequence of changes from a single database.

Supported version

With this agent, you can target any version of YugabyteDB starting from 2.0.

Change data capture

Works on any version of YugabyteDB starting from 2.0.

Platform supported features

Feature	Support	Notes
Target role	✅	Writes to YugabyteDB via the smart JDBC driver with topology-aware routing and TLS.
Source role	✅	Consumes logical decoding streams from YugabyteDB replication slots.
Snapshots	✅	Snapshot jobs seed YugabyteDB tables before CDC resumes.
CDC	✅	Streams WAL-derived logical changes in near real time.
CDC type	Replication slots / logical decoding	Leverages YugabyteDB-compatible PostgreSQL logical decoding APIs.
User defined data types	✅	Supports user defined data types.
Bulk load	✅	Smart driver batching covers high-throughput needs; no dedicated staging flow.
Source persisted internal cache	N/A	Offsets are tracked in Core Hub metadata plus replication slot positions.
Target persisted internal cache	N/A	Writes go straight to YugabyteDB; no local disk cache.
Driver / connector	YugabyteDB smart JDBC driver	Provides load balancing, node failover, and TLS support.
Chains	N/A	Not supported.
Truncate operation support (reading)	✅	Logical decoding surfaces TRUNCATE events which are forwarded downstream.
Truncate operation support (writing)	✅	Supports Core Hub “TRUNCATE before snapshot” behavior when targeting YugabyteDB.

Feature

Support

Notes

Target role

✅

Writes to YugabyteDB via the smart JDBC driver with topology-aware routing and TLS.

Source role

✅

Consumes logical decoding streams from YugabyteDB replication slots.

Snapshots

✅

Snapshot jobs seed YugabyteDB tables before CDC resumes.

CDC

✅

Streams WAL-derived logical changes in near real time.

CDC type

Replication slots / logical decoding

Leverages YugabyteDB-compatible PostgreSQL logical decoding APIs.

User defined data types

✅

Supports user defined data types.

Bulk load

✅

Smart driver batching covers high-throughput needs; no dedicated staging flow.

Source persisted internal cache

N/A

Offsets are tracked in Core Hub metadata plus replication slot positions.

Target persisted internal cache

N/A

Writes go straight to YugabyteDB; no local disk cache.

Driver / connector

YugabyteDB smart JDBC driver

Provides load balancing, node failover, and TLS support.

Chains

N/A

Not supported.

Truncate operation support (reading)

✅

Logical decoding surfaces TRUNCATE events which are forwarded downstream.

Truncate operation support (writing)

✅

Supports Core Hub “TRUNCATE before snapshot” behavior when targeting YugabyteDB.