Search docs.molo17.com
    A newer version of this documentation is available.
    View Latest (v2.3)

    Aerospike Agent for Gluesync: Features & Compatibility

    Static

    Core principles

    Gluesync’s Aerospike agent uses and implements the Aerospike Java SDK to connect and perform all the operations at the node/cluster level. Gluesync also supports Aerospike HA features as well as load balancing across multiple cluster nodes, thanks to automatic node discovery.

    Change data capture

    This agent implements the ESP connector provided by Aerospike to catch real-time data changes from Aerospike’s namespaces starting from Database Server version 7.0 and above.

    Security

    Starting from Gluesync 1.5 the replication supports secure communication via TLS encryption when connecting to the Aerospike cluster, this can be optionally enabled depending on your configuration and use case. We recommend adopting TLS encryption for any production use case.

    Supported version

    Works with Aerospike 6.5 and above, hosted on-prem or in Aerospike DBaaS. Both Community Edition (CE) and Enterprise Edition (EE) are supported.

    Platform supported features

    Feature Support Notes

    Target role

    ✅

    Writes to Aerospike via the official Java SDK with TLS and automatic node discovery/load balancing.

    Source role

    ✅ (Not publicy available, please reach out to Gluesync support for more details)

    Consumes Aerospike ESP/XDR streams to capture namespace changes in real time.

    Snapshots

    ✅

    Supports full snapshot exports/imports for seeding Aerospike sets before CDC resumes.

    CDC

    ✅

    Real-time replication powered by the ESP connector (docs).

    CDC type

    ESP / XDR streams

    Uses Aerospike’s Event Stream Processing connector for low-latency change delivery.

    Bulk load

    N/A

    SDK streaming handle throughput, uses built-in bulk operations for large batches; no staging-table bulk workflow required.

    Source persisted internal cache

    N/A

    State is tracked in Core Hub metadata; agent keeps no disk cache.

    Target persisted internal cache

    N/A

    Writes are applied directly to Aerospike without intermediate buffers.

    Driver / connector

    Aerospike Java SDK

    Vendor-supported integration bundled with Gluesync.

    Chains

    N/A

    Not supported being it a NoSQL database.

    Truncate operation support (reading)

    N/A

    Aerospike streams emit record-level changes; namespace TRUNCATE isn’t surfaced.

    Truncate operation support (writing)

    N/A

    Gluesync does not issue TRUNCATE/TRUNCATE namespace commands automatically.