Azure Cosmos DB Agent for Gluesync: Features & Compatibility
Core principles
Gluesync’s Azure Cosmos DB agent depends on the Microsoft Azure Java SDK (azure-cosmos) to connect with the Azure Cosmos DB and interact through its SQL API.
Change data capture
This agent implements the Azure Cosmos DB Change feed processor which is part of the Azure V4 SDK to catch real-time data changes from Cosmos DB. Starting from Gluesync 2.3 the change feed is read in the all versions and deletes mode: inserts, updates and deletes (including the ones due to TTL expiry) are captured natively and every intermediate change is delivered in order, with no soft-delete field and no Azure Function required.
The mode requires the Azure Cosmos DB for NoSQL API and continuous backup on the account. See Enabling the all versions and deletes change feed mode and the limitations.
| Breaking change in Gluesync 2.3: soft-delete support is removed. See Upgrading from Gluesync 2.2. |
Supported version
Works with Azure Cosmos DB DBaaS, any region. As a source, the account must use the API for NoSQL, with continuous backup and the all versions and deletes change feed mode enabled.
Platform supported features
| Feature | Support | Notes |
|---|---|---|
Target role |
✅ |
Uses the Azure Cosmos Java SDK (SQL API) with TLS and auto-failover awareness. |
Source role |
✅ |
Consumes the Change Feed processor in all versions and deletes mode to capture inserts, updates and deletes (including TTL expiry) in real time. |
Snapshots |
✅ |
Supports full snapshot tasks to seed Cosmos containers prior to CDC. |
CDC |
✅ |
Continuous replication based on the Cosmos Change Feed in all versions and deletes mode (V4 SDK). |
CDC type |
Change Feed processor (all versions and deletes) |
Built on Microsoft’s native Change Feed implementation; no soft-delete field is required. |
Bulk load |
N/A |
Document writes stream via SDK batching; no staging-table bulk workflow. |
Database pooling |
✅ |
Supports connection pooling for efficient resource utilization across multiple pipelines. |
Source persisted internal cache |
N/A |
State is maintained in Core Hub metadata; no disk cache required. |
Target persisted internal cache |
N/A |
Writes are flushed directly to Cosmos DB via the SDK. |
Driver / connector |
Azure Cosmos Java SDK |
Gluesync embeds the official |
Chains |
N/A |
Not supported being it a NoSQL database. |
Truncate operation support (reading) |
N/A |
Change Feed exposes record-level operations only; no TRUNCATE semantics. |
Truncate operation support (writing) |
N/A |
The agent does not issue container-wide truncations automatically. |