Real-time
Two-way sync
Changes in Google Cloud Spanner or SingleStore instantly reflect in both systems. No stale data, no manual imports.
Database
Google Cloud Spanner to SingleStore integration — real-time, two-way sync
Keep Google Cloud Spanner and SingleStore 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 SingleStore
Keep Google Cloud Spanner and SingleStore 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 SingleStore 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 Sync results of real-time analytical queries back into business tools where teams act on them.
- 04 Consolidate data from transactional databases and SaaS apps into one store that handles both lookups and scans.
Common sync patterns
Cross-engine sync
Keep the same dataset live in both Google Cloud Spanner and SingleStore, 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 SingleStore
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 | SingleStore objects | How this pairing syncs | |
|---|---|---|---|
| Databases Top-level containers that scope schema and sync configuration. | Databases The connection target containing the tables a sync addresses. | 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 as curated sync sources. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables Relational tables mapped one-to-one to sync targets. | Tables (rowstore and columnstore) Primary read/write target; storage type affects whether a table suits point lookups or scans. | Tables is specific to Google Cloud Spanner and Tables (rowstore and columnstore) to SingleStore — 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. | Reference Tables Small tables replicated to every node, often used for dimension data in syncs. | Rows is specific to Google Cloud Spanner and Reference Tables to SingleStore — 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. | Pipelines Native ingestion jobs from Kafka or object storage that coexist with external syncs. | Interleaved tables is specific to Google Cloud Spanner and Pipelines to SingleStore — 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. | Stored Procedures Existing logic sometimes invoked on write paths. | Secondary indexes is specific to Google Cloud Spanner and Stored Procedures to SingleStore — each maps to any object or custom field on the other side. |
How changes propagate between Google Cloud Spanner and SingleStore
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 SingleStore 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 SingleStore as a row-level write, with types converted between the two schemas.
SingleStore Google Cloud Spanner Interval-based propagation
DetectionStacksync polls SingleStore for changes on an incremental schedule, reading only records changed since the previous pass. Polling on timestamp or watermark columns.
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.
- SingleStore: No API rate limits; throughput is bounded by workspace or cluster size.
What ships with Google Cloud Spanner ⇄ SingleStore
Connect Google Cloud Spanner and SingleStore for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–SingleStore connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Google Cloud Spanner or SingleStore 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 SingleStore record.
Observability
Monitoring
Track your Google Cloud Spanner ⇄ SingleStore 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 SingleStore.
How the Google Cloud Spanner and SingleStore 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.
SingleStore
- Integration surface
- SQL over the MySQL wire protocol; an HTTP Data API is also available for SQL over REST
- Authentication
- Database credentials
- Change detection
- Polling on timestamp or watermark columns; the platform also provides change-observation features in recent versions
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by workspace or cluster size
How it works
How to connect Google Cloud Spanner to SingleStore — 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.
- 01
Connect your apps
Authenticate Google Cloud Spanner and SingleStore with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Google Cloud Spanner
connected
SingleStore
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Google Cloud Spanner and SingleStore 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.
objects · Google Cloud Spanner ⇄ SingleStoreCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Google Cloud Spanner SingleStoreCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Google Cloud Spanner and SingleStore integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Spanner and SingleStore: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Databases and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 SingleStore 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 SingleStore connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Google Cloud Spanner–SingleStore integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Google Cloud Spanner and SingleStore. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Google Cloud Spanner: Change streams (log-style CDC), or timestamp-based polling queries. On SingleStore: Polling on timestamp or watermark columns; the platform also provides change-observation features in recent versions. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Google Cloud Spanner side: Interleaved tables, Secondary indexes, Change streams, Views, plus custom fields where Google Cloud Spanner exposes them. On the SingleStore side: Pipelines, Stored Procedures, Indexes and Shard Keys, Databases. Stacksync auto-detects both schemas and converts types between the two systems.
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.
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:
