Two-way sync
Changes in Google Cloud Spanner or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner and Scaleway Postgres 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 Scaleway Postgres 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 Google Cloud Spanner and Scaleway Postgres, 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.
| Google Cloud Spanner objects | Scaleway Postgres objects | How this pairing syncs | |
|---|---|---|---|
| Tables Relational tables mapped one-to-one to sync targets. | Tables Primary sync unit; each table maps to an object or table on the other side of the sync. | 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 sources for shaping data before it leaves the database. | 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. | Sequences Generate primary keys; sync tooling must respect them when writing rows. | Databases is specific to Google Cloud Spanner and Sequences to Scaleway Postgres — 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. | Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | Rows is specific to Google Cloud Spanner and Columns to Scaleway Postgres — 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. | Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. | Interleaved tables is specific to Google Cloud Spanner and Materialized views to Scaleway Postgres — 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 Namespace tables so multiple applications or environments can be synced selectively. | Secondary indexes is specific to Google Cloud Spanner and Schemas to Scaleway Postgres — each maps to any object or custom field on the other side. |
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.
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 Scaleway Postgres as a row-level write, with types converted between the two schemas.
DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.
DeliveryEach detected change is applied to Google Cloud Spanner as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Scaleway Postgres connection.
Changes in Google Cloud Spanner or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or Scaleway Postgres 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 Scaleway Postgres record.
Track your Google Cloud Spanner ⇄ Scaleway Postgres sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Scaleway Postgres.
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 Scaleway Postgres 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 Scaleway Postgres 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 Scaleway Postgres: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Google Cloud Spanner: Change streams (log-style CDC), or timestamp-based polling queries. On Scaleway Postgres: Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling. 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: Secondary indexes, Change streams, Views, Databases, plus custom fields where Google Cloud Spanner exposes them. On the Scaleway Postgres side: Tables, Views, Materialized views, Schemas. 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 Google Cloud Spanner and Scaleway Postgres: 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.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Scaleway Postgres: SQL wire protocol (PostgreSQL). Authentication: Database credentials (username/password over TLS). Stacksync manages authentication, retries, and rate limits on both sides.
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 366 integrations available for Google Cloud Spanner and Scaleway Postgres.