Skip to content
Database

OCI Database (Oracle Cloud) to TiDB integration — real-time, two-way sync

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.

  • 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 OCI Database (Oracle Cloud) and TiDB

Keep OCI Database (Oracle Cloud) 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 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.

Common use cases

  • Run on-prem Oracle and OCI side by side during a cloud migration while keeping both ends writable.
  • Expose ERP or billing data held in OCI to internal tools by syncing selected schemas to a managed Postgres.
  • Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas

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 OCI Database (Oracle Cloud) 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.

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.
What ships with OCI Database (Oracle Cloud) ⇄ TiDB

Connect OCI Database (Oracle Cloud) and TiDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–TiDB connection.

Real-time

Two-way sync

Changes in OCI Database (Oracle Cloud) or TiDB instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) or TiDB record.

Observability

Monitoring

Track your OCI Database (Oracle Cloud) ⇄ TiDB sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) and TiDB.

How the OCI Database (Oracle Cloud) and TiDB connectors work

OCI Database (Oracle Cloud)

Integration surface
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
Change detection
log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
Capabilities
read · write · CDC
Rate limits
throughput bounded by instance sizing rather than API quotas

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 OCI Database (Oracle Cloud) 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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    OCI Database (Oracle Cloud) connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · OCI Database (Oracle Cloud) ⇄ TiDB
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    OCI Database (Oracle Cloud) TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

OCI Database (Oracle Cloud) and TiDB integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for OCI Database (Oracle Cloud) and TiDB.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.