Skip to content
Database

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

Keep Google Cloud Spanner and OCI Database (Oracle Cloud) 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 Google Cloud Spanner and OCI Database (Oracle Cloud)

Keep Google Cloud Spanner and OCI Database (Oracle Cloud) 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 Google Cloud Spanner and OCI Database (Oracle Cloud) 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 Consolidate data from a globally distributed Spanner deployment into regional business systems.
  • 02 Push billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.
  • 03 Run on-prem Oracle and OCI side by side during a cloud migration while keeping both ends writable.
  • 04 Expose ERP or billing data held in OCI to internal tools by syncing selected schemas to a managed Postgres.

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 Google Cloud Spanner and OCI Database (Oracle Cloud)

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.

Google Cloud Spanner objects OCI Database (Oracle Cloud) objects How this pairing syncs
Tables Relational tables mapped one-to-one to sync targets. Tables The primary sync surface; rows are read and written directly over SQL Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Views Read-only projections useful for shaping data before it leaves Spanner. Views Read-only projections used to expose curated subsets to downstream systems Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Secondary indexes Used to make incremental read queries efficient on non-key columns. Partitions Physical table subdivisions relevant when replicating large fact tables Secondary indexes is specific to Google Cloud Spanner and Partitions to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Change streams Capture inserts, updates, and deletes for log-style change data capture. Materialized views Precomputed result sets sometimes used as stable read sources for replication Change streams is specific to Google Cloud Spanner and Materialized views to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Databases Top-level containers that scope schema and sync configuration. Schemas Namespace boundaries that scope which objects a sync connection can access Databases is specific to Google Cloud Spanner and Schemas to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.
Rows The unit of read and write in each sync cycle, keyed by primary key. Sequences Key generators that matter when writing new rows from external systems Rows is specific to Google Cloud Spanner and Sequences to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and OCI Database (Oracle Cloud)

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.

Google Cloud Spanner OCI Database (Oracle Cloud) Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

DeliveryEach detected change is applied to OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.

OCI Database (Oracle Cloud) Google Cloud Spanner Sub-second propagation

DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.

DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
What ships with Google Cloud Spanner ⇄ OCI Database (Oracle Cloud)

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Google Cloud Spanner and OCI Database (Oracle Cloud) connectors work

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.

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
How it works

How to connect Google Cloud Spanner to OCI Database (Oracle Cloud) — 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 Google Cloud Spanner and OCI Database (Oracle Cloud) 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
    Google Cloud Spanner connected
    OCI Database (Oracle Cloud) connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud Spanner and OCI Database (Oracle Cloud) 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 · Google Cloud Spanner ⇄ OCI Database (Oracle Cloud)
    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
    Google Cloud Spanner OCI Database (Oracle Cloud)
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Google Cloud Spanner and OCI Database (Oracle Cloud) integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 357 integrations available for Google Cloud Spanner and OCI Database (Oracle Cloud).

Popular · 3 of 357
All Google Cloud Spanner integrations All OCI Database (Oracle Cloud) integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own