Real-time
Two-way sync
Changes in Azure Cosmos DB or TiDB instantly reflect in both systems. No stale data, no manual imports.
Database
Azure Cosmos DB to TiDB integration — real-time, two-way sync
Keep Azure Cosmos DB and TiDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Azure Cosmos DB and TiDB
Keep Azure Cosmos DB and TiDB synchronized in real time, across engines, regions, or services, in one or both directions.
Two databases that must agree is one of the oldest problems in engineering: different engines for different workloads, separate services with overlapping reference data, a migration in flight, or regional instances that share a subset of records. Hand-rolled replication across systems means change capture, conflict handling, and type mapping, all built and maintained by your team.
Stacksync syncs tables or collections between Azure Cosmos DB and TiDB continuously and bi-directionally, translating types between the two engines and resolving conflicts by rules you configure. Rows written on either side appear on the other within seconds.
Common use cases
- 01 Mirror Cosmos DB items into Postgres so teams can query operational data with standard SQL.
- 02 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
- 03 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
- 04 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
Common sync patterns
Migration with zero-downtime cutover
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Shared reference data between services
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Regional or environment copies
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
What you can sync between Azure Cosmos DB and TiDB
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Azure Cosmos DB objects | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Databases Top-level namespaces that scope containers and throughput provisioning. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Columns MySQL-compatible types mapped to fields in the paired system. | Stored procedures and triggers is specific to Azure Cosmos DB and Columns to TiDB — each maps to any object or custom field on the other side. | |
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Indexes Secondary indexes that keep incremental sync queries efficient. | Containers is specific to Azure Cosmos DB and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Sequences Server-side ID generation relevant when external systems write rows. | Items (JSON documents) is specific to Azure Cosmos DB and Sequences to TiDB — each maps to any object or custom field on the other side. | |
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Partition keys is specific to Azure Cosmos DB and Tables to TiDB — each maps to any object or custom field on the other side. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Views Logical views for shaping reads before syncing outward. | Change feed entries is specific to Azure Cosmos DB and Views to TiDB — each maps to any object or custom field on the other side. |
How changes propagate between Azure Cosmos DB and TiDB
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Azure Cosmos DB TiDB Sub-second propagation
DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.
DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.
TiDB Azure Cosmos DB Sub-second propagation
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
DeliveryEach detected change is applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Azure Cosmos DB ⇄ TiDB
Connect Azure Cosmos DB and TiDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–TiDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Cosmos DB or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Azure Cosmos DB or TiDB record.
Observability
Monitoring
Track your Azure Cosmos DB ⇄ TiDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and TiDB.
How the Azure Cosmos DB and TiDB connectors work
Azure Cosmos DB
- Integration surface
- REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
- Authentication
- Account keys, resource tokens, or Microsoft Entra ID role-based access
- Change detection
- Built-in change feed exposing inserts and updates in order within each partition key range
- Capabilities
- read · write · CDC
TiDB
- Integration surface
- MySQL wire protocol (SQL)
- Authentication
- Database credentials (MySQL-compatible username/password)
- Change detection
- Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
- Capabilities
- read · write · CDC
- Rate limits
- Throughput scales with cluster size rather than fixed API quotas
How it works
How to connect Azure Cosmos DB to TiDB — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Azure Cosmos DB and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Azure Cosmos DB
connected
TiDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Cosmos DB and TiDB objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Azure Cosmos DB ⇄ TiDBCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Azure Cosmos DB TiDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Cosmos DB and TiDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Cosmos DB and TiDB: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Databases and Stored procedures and triggers), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Azure Cosmos DB: Throughput is provisioned in request units per container or database, which means sync read and write volume has a direct cost and throttling dimension. TiDB: TiCDC provides ordered row-level change capture and delivers to sinks such as Kafka or MySQL-compatible targets. Stacksync's field mapping accounts for these differences between Azure Cosmos DB and TiDB without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Azure Cosmos DB and TiDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Cosmos DB and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Cosmos DB–TiDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Azure Cosmos DB and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Azure Cosmos DB: Built-in change feed exposing inserts and updates in order within each partition key range. On TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 363 integrations available for Azure Cosmos DB and TiDB.
Popular · 3 of 363
No integrations match .
