Two-way sync
Changes in Citus or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Keep Citus and Google Cloud Spanner 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 Citus and Google Cloud Spanner 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.
Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
Keep the same dataset live in both Citus and Google Cloud Spanner, so each workload runs on the engine that suits it.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
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.
| Citus objects | Google Cloud Spanner objects | |
|---|---|---|
| Sequences Key generators that matter when external writes must not collide with application inserts. | Tables Relational tables mapped one-to-one to sync targets. | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | Rows The unit of read and write in each sync cycle, keyed by primary key. | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Interleaved tables Child rows physically co-located with parents; synced as related records. | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Secondary indexes Used to make incremental read queries efficient on non-key columns. | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Change streams Capture inserts, updates, and deletes for log-style change data capture. | |
| Views Curated projections over distributed data, often used as read-only sync sources. | Views Read-only projections useful for shaping data before it leaves Spanner. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Google Cloud Spanner connection.
Changes in Citus or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus or Google Cloud Spanner data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Citus or Google Cloud Spanner record.
Track your Citus ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus and Google Cloud Spanner.
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 Citus and Google Cloud Spanner 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 Citus and Google Cloud Spanner 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 Citus and Google Cloud Spanner: authenticate both systems, choose the objects to sync (such as Citus's Sequences and Distributed tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Citus and Google Cloud Spanner. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. On Google Cloud Spanner: Change streams (log-style CDC), or timestamp-based polling queries. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Citus side: Sequences, Distributed tables, Reference tables, Local tables, plus custom fields where Citus exposes them. On the Google Cloud Spanner side: Tables, Rows, Interleaved tables, Secondary indexes. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Citus and Google Cloud Spanner: Regional or environment copies; Cross-engine sync; Migration with zero-downtime cutover. Mirror selected tables to another region or environment continuously, filtered to just the rows that should travel.
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 Citus and Google Cloud Spanner.