Skip to content
Database

Google Cloud Spanner to MariaDB integration — real-time, two-way sync

Keep Google Cloud Spanner and MariaDB 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 MariaDB

Keep Google Cloud Spanner and MariaDB 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 MariaDB 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 Push billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.
  • 02 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • 03 Replicate ERP or billing master data into MariaDB databases that power customer-facing applications
  • 04 Feed a warehouse continuously from MariaDB using binlog-based capture instead of scheduled dumps

Common sync patterns

Cross-engine sync

Keep the same dataset live in both Google Cloud Spanner and MariaDB, so each workload runs on the engine that suits it.

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.

What you can sync between Google Cloud Spanner and MariaDB

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 MariaDB objects How this pairing syncs
Tables Relational tables mapped one-to-one to sync targets. Tables The primary sync target; rows map to records in connected systems. 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-side projections used as outbound sync sources. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Databases Top-level containers that scope schema and sync configuration. Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. Databases is specific to Google Cloud Spanner and Databases (Schemas) to MariaDB — 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. Columns Field-level mapping targets with engine-typed values. Rows is specific to Google Cloud Spanner and Columns to MariaDB — each maps to any object or custom field on the other side.
Interleaved tables Child rows physically co-located with parents; synced as related records. Primary and Unique Keys Match keys for idempotent upserts. Interleaved tables is specific to Google Cloud Spanner and Primary and Unique Keys to MariaDB — each maps to any object or custom field on the other side.
Secondary indexes Used to make incremental read queries efficient on non-key columns. System-Versioned Tables Temporal tables that retain row history natively, useful for auditing synced changes. Secondary indexes is specific to Google Cloud Spanner and System-Versioned Tables to MariaDB — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud Spanner and MariaDB

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 MariaDB 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 MariaDB as a row-level write, with types converted between the two schemas.

MariaDB Google Cloud Spanner Sub-second propagation

DetectionChanges in MariaDB are captured at the source via change data capture — no polling loop against its API. Database triggers — Stacksync creates deterministic triggers for internal logging and syncing.

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.
  • MariaDB: No API rate limits; throughput is bounded by connection limits and server resources.
What ships with Google Cloud Spanner ⇄ MariaDB

Connect Google Cloud Spanner and MariaDB for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–MariaDB connection.

Real-time

Two-way sync

Changes in Google Cloud Spanner or MariaDB 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 MariaDB 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 MariaDB record.

Observability

Monitoring

Track your Google Cloud Spanner ⇄ MariaDB 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 MariaDB.

How the Google Cloud Spanner and MariaDB 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.

MariaDB

Integration surface
SQL wire protocol (MySQL-compatible client/server protocol)
Authentication
Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host)
Change detection
Database triggers — Stacksync creates deterministic triggers for internal logging and syncing
Capabilities
read · write · CDC
Rate limits
No API rate limits; throughput is bounded by connection limits and server resources
MariaDB setup guide
How it works

How to connect Google Cloud Spanner to MariaDB — 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 MariaDB 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
    MariaDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Google Cloud Spanner and MariaDB 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 366 integrations available for Google Cloud Spanner and MariaDB.

Popular · 5 of 366
All Google Cloud Spanner integrations All MariaDB 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