Real-time
Two-way sync
Changes in Google Cloud Spanner or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Database
Google Cloud Spanner to TimescaleDB integration — real-time, two-way sync
Keep Google Cloud Spanner and TimescaleDB 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 TimescaleDB
Keep Google Cloud Spanner and TimescaleDB 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 TimescaleDB 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 Replicate subscription and billing events from operational Postgres tables into Timescale hypertables for time-series analysis.
- 04 Keep device or asset reference tables bi-directionally in sync between TimescaleDB and an ERP.
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 TimescaleDB
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 | TimescaleDB objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-only projections useful for shaping data before it leaves Spanner. | Views Standard SQL views used to shape or filter data for consumers. | 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. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | Databases is specific to Google Cloud Spanner and Hypertables to TimescaleDB — each maps to any object or custom field on the other side. | |
| Tables Relational tables mapped one-to-one to sync targets. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | Tables is specific to Google Cloud Spanner and Chunks to TimescaleDB — 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. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | Rows is specific to Google Cloud Spanner and Continuous Aggregates to TimescaleDB — 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. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | Interleaved tables is specific to Google Cloud Spanner and Regular PostgreSQL Tables to TimescaleDB — 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. | Schemas Postgres namespaces used to separate synced datasets by team or environment. | Secondary indexes is specific to Google Cloud Spanner and Schemas to TimescaleDB — each maps to any object or custom field on the other side. |
How changes propagate between Google Cloud Spanner and TimescaleDB
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 TimescaleDB 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 TimescaleDB as a row-level write, with types converted between the two schemas.
TimescaleDB Google Cloud Spanner Sub-second propagation
DetectionChanges in TimescaleDB are captured at the source via change data capture — no polling loop against its API. Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must.
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.
- TimescaleDB: No API rate limits; throughput is bounded by database resources and connection limits.
What ships with Google Cloud Spanner ⇄ TimescaleDB
Connect Google Cloud Spanner and TimescaleDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–TimescaleDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Google Cloud Spanner or TimescaleDB 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 TimescaleDB record.
Observability
Monitoring
Track your Google Cloud Spanner ⇄ TimescaleDB 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 TimescaleDB.
How the Google Cloud Spanner and TimescaleDB 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.
TimescaleDB
- Integration surface
- SQL wire protocol (PostgreSQL)
- Authentication
- Database credentials
- Change detection
- Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication
- Capabilities
- read · write · CDC
- Rate limits
- No API rate limits; throughput is bounded by database resources and connection limits.
How it works
How to connect Google Cloud Spanner to TimescaleDB — 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 TimescaleDB 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
TimescaleDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Google Cloud Spanner and TimescaleDB 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 ⇄ TimescaleDBCustomers 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 TimescaleDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Google Cloud Spanner and TimescaleDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Spanner and TimescaleDB: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Views and Databases), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Google Cloud Spanner: Change streams record row-level inserts, updates, and deletes and can be consumed through the API for CDC pipelines. TimescaleDB: Hypertables automatically partition rows into time-based chunks while inserts and queries target the parent table. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and TimescaleDB 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 TimescaleDB 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 TimescaleDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Google Cloud Spanner–TimescaleDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Google Cloud Spanner and TimescaleDB. 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 TimescaleDB: Log-based capture via PostgreSQL logical decoding where the deployment allows it — hypertable changes surface on the underlying chunk tables and must be remapped to the parent — or timestamp-based polling on time columns; regular Postgres tables replicate through standard logical replication. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 352 integrations available for Google Cloud Spanner and TimescaleDB.
Popular · 3 of 352
No integrations match .
