Two-way sync
Changes in Google Cloud Spanner or MySQL instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and MySQL 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 Google Cloud Spanner and MySQL 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.
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.
Keep the same dataset live in both Google Cloud Spanner and MySQL, so each workload runs on the engine that suits it.
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 | MySQL objects | |
|---|---|---|
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Columns Field-level mapping targets with engine-typed values. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | Primary and Unique Keys Match keys for idempotent upserts and conflict handling. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | JSON Columns Validated semi-structured payloads for nested SaaS data. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Stored Procedures Server-side logic that can post-process synced rows. | |
| Databases Top-level containers that scope schema and sync configuration. | Triggers An alternative change-capture mechanism when binlog access is unavailable. | |
| Tables Relational tables mapped one-to-one to sync targets. | Databases (Schemas) Top-level namespaces that scope a sync's reads and writes. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–MySQL connection.
Changes in Google Cloud Spanner or MySQL instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or MySQL data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or MySQL record.
Track your Google Cloud Spanner ⇄ MySQL sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and MySQL.
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 Google Cloud Spanner and MySQL 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 Google Cloud Spanner and MySQL 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 Google Cloud Spanner and MySQL: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Interleaved tables and Secondary indexes), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Google Cloud Spanner and MySQL: Shared reference data between services; Regional or environment copies; Cross-engine sync. Services that own separate databases stay consistent on the records they share, without a custom replication layer.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). MySQL: SQL wire protocol (MySQL client/server protocol). Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host). Stacksync manages authentication, retries, and rate limits on both sides.
Google Cloud Spanner: It supports two SQL dialects: GoogleSQL and a PostgreSQL-interface dialect chosen at database creation. MySQL: Composite primary keys are not supported — primary key must be a single column. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and MySQL 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 Google Cloud Spanner and MySQL records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Google Cloud Spanner and MySQL connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Google Cloud Spanner–MySQL integration in-house.
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 Google Cloud Spanner and MySQL.