Two-way sync
Changes in DuckDB or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB 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 DuckDB 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.
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.
Keep the same dataset live in both DuckDB and Google Cloud Spanner, so each workload runs on the engine that suits it.
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.
| DuckDB objects | Google Cloud Spanner objects | |
|---|---|---|
| Views SQL views used to shape or filter data for downstream consumers. | Databases Top-level containers that scope schema and sync configuration. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Tables Relational tables mapped one-to-one to sync targets. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Rows The unit of read and write in each sync cycle, keyed by primary key. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Interleaved tables Child rows physically co-located with parents; synced as related records. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Secondary indexes Used to make incremental read queries efficient on non-key columns. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Change streams Capture inserts, updates, and deletes for log-style change data capture. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Google Cloud Spanner connection.
Changes in DuckDB or Google Cloud Spanner instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB 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 DuckDB or Google Cloud Spanner record.
Track your DuckDB ⇄ Google Cloud Spanner sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB 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 DuckDB 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 DuckDB 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 DuckDB and Google Cloud Spanner: authenticate both systems, choose the objects to sync (such as DuckDB's Views and External files (Parquet/CSV/JSON)), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the DuckDB side: External files (Parquet/CSV/JSON), Attached databases, Database files, Schemas, plus custom fields where DuckDB exposes them. On the Google Cloud Spanner side: Secondary indexes, Change streams, Views, Databases. 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 DuckDB and Google Cloud Spanner: Shared reference data between services; Regional or environment copies; Cross-engine sync. Services that own separate databases stay consistent on the records they share, without a custom replication layer.
DuckDB: In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default. Authentication: None built in; access control is file-system level (MotherDuck adds token auth for its hosted service). Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Stacksync manages authentication, retries, and rate limits on both sides.
DuckDB: Concurrency is single-writer: one process holds write access to a database file at a time, which shapes how sync jobs schedule writes. Google Cloud Spanner: Interleaved tables physically store child rows with their parent rows, which affects how related records are read. Stacksync's field mapping accounts for these differences between DuckDB and Google Cloud Spanner without custom code.
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 DuckDB and Google Cloud Spanner.