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.
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 to capture inserts/updates/deletes in real time. |
Snapshots |
✅ |
Supports full snapshot tasks to seed Cosmos containers prior to CDC. |
CDC |
✅ |
Continuous replication based on the Cosmos Change Feed (V4 SDK). |
CDC type |
Change Feed processor |
Built on Microsoft’s native Change Feed implementation. |
Bulk load |
N/A |
Document writes stream via SDK batching; no staging-table bulk workflow. |
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. |