Two-way sync
Changes in DuckDB or Dynamo DB instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and Dynamo DB 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 Dynamo DB 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 DuckDB and Dynamo DB, 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.
| DuckDB objects | Dynamo DB objects | |
|---|---|---|
| Views SQL views used to shape or filter data for downstream consumers. | Global Tables Multi-region replicas relevant when syncs must read from a specific region. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Tables The top-level containers a sync targets; each table is addressed independently. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Attributes Per-item fields, including nested maps and lists, flattened or mapped during sync. | |
| Schemas Namespaces within a database used to organize tables in sync outputs. | Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–Dynamo DB connection.
Changes in DuckDB or Dynamo DB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or Dynamo DB 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 Dynamo DB record.
Track your DuckDB ⇄ Dynamo DB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and Dynamo DB.
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 Dynamo DB 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 Dynamo DB 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 Dynamo DB: 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.
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 Dynamo DB: 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.
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). Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. 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. Dynamo DB: PartiQL provides a SQL-compatible query layer over the same key-based access model. Stacksync's field mapping accounts for these differences between DuckDB and Dynamo DB 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 DuckDB and Dynamo DB records are not retained after a sync operation.
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 Dynamo DB.