Two-way sync
Changes in OCI Database (Oracle Cloud) or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep OCI Database (Oracle Cloud) 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.
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 OCI Database (Oracle Cloud) 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.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
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.
| OCI Database (Oracle Cloud) objects | TiDB objects | |
|---|---|---|
| Materialized views Precomputed result sets sometimes used as stable read sources for replication | Columns MySQL-compatible types mapped to fields in the paired system. | |
| Schemas Namespace boundaries that scope which objects a sync connection can access | Indexes Secondary indexes that keep incremental sync queries efficient. | |
| Sequences Key generators that matter when writing new rows from external systems | Sequences Server-side ID generation relevant when external systems write rows. | |
| PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Databases MySQL-style schemas addressed by any MySQL-compatible client. | |
| JSON collections Document-style storage in the converged engine, synced alongside relational tables | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | |
| Partitions Physical table subdivisions relevant when replicating large fact tables | Views Logical views for shaping reads before syncing outward. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–TiDB connection.
Changes in OCI Database (Oracle Cloud) or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever OCI Database (Oracle Cloud) or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single OCI Database (Oracle Cloud) or TiDB record.
Track your OCI Database (Oracle Cloud) ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) and TiDB.
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.
Authenticate OCI Database (Oracle Cloud) 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.
Pick the OCI Database (Oracle Cloud) 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between OCI Database (Oracle Cloud) and TiDB: authenticate both systems, choose the objects to sync (such as OCI Database (Oracle Cloud)'s Materialized views and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for OCI Database (Oracle Cloud) and TiDB: Migration with zero-downtime cutover; Shared reference data between services; Regional or environment copies. When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
OCI Database (Oracle Cloud): SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP. Authentication: Database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
OCI Database (Oracle Cloud): OCI database services run the same Oracle Database engine as on-premises installs, so PL/SQL, sequences, and redo-log CDC behave identically to self-managed Oracle. TiDB: TiFlash maintains columnar replicas of row data, letting analytical queries run on current data without a separate warehouse. Stacksync's field mapping accounts for these differences between OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) and TiDB records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for OCI Database (Oracle Cloud) and TiDB.