Two-way sync
Changes in Google Cloud Spanner or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
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.
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.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
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.
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 | |
|---|---|---|
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Hypertables Time-partitioned tables that hold the main time-series data; the primary read and write target in syncs. | |
| Secondary indexes Used to make incremental read queries efficient on non-key columns. | Chunks Time-bounded partitions of a hypertable; syncs read and write through the parent hypertable and never address chunks directly. | |
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Continuous Aggregates Incrementally maintained rollups that serve as pre-aggregated read sources for downstream systems. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Regular PostgreSQL Tables Relational reference data such as devices, tenants, or accounts synced alongside the series data. | |
| Databases Top-level containers that scope schema and sync configuration. | Views Standard SQL views used to shape or filter data for consumers. | |
| Tables Relational tables mapped one-to-one to sync targets. | Schemas Postgres namespaces used to separate synced datasets by team or environment. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–TimescaleDB connection.
Changes in Google Cloud Spanner or TimescaleDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or TimescaleDB 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 TimescaleDB record.
Track your Google Cloud Spanner ⇄ TimescaleDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and TimescaleDB.
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 TimescaleDB 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 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.
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 TimescaleDB: 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.
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.
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 TimescaleDB.