Two-way sync
Changes in DuckDB or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and IBM AS/400 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 IBM AS/400 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 IBM AS/400, 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 | IBM AS/400 objects | |
|---|---|---|
| Schemas Namespaces within a database used to organize tables in sync outputs. | Libraries The schema-equivalent containers that scope which files a sync reads. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Physical files (tables) The Db2 for i tables mapped directly to sync targets. | |
| Views SQL views used to shape or filter data for downstream consumers. | Logical files (views) Indexed or filtered views over physical files, usable as read sources. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Members Sub-partitions of files in legacy applications, flattened or selected during syncs. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Rows / records The unit of read and write, accessed via SQL or record-level access. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Journals and journal receivers The change log that enables log-based CDC on journaled files. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–IBM AS/400 connection.
Changes in DuckDB or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or IBM AS/400 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 IBM AS/400 record.
Track your DuckDB ⇄ IBM AS/400 sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and IBM AS/400.
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 IBM AS/400 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 IBM AS/400 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 IBM AS/400: authenticate both systems, choose the objects to sync (such as DuckDB's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
DuckDB: Concurrency is single-writer: one process holds write access to a database file at a time, which shapes how sync jobs schedule writes. IBM AS/400: Journaling writes row-level before/after images to journal receivers, which is the basis for log-based CDC on IBM i. Stacksync's field mapping accounts for these differences between DuckDB and IBM AS/400 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 IBM AS/400 records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and IBM AS/400 connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–IBM AS/400 integration in-house.
Yes — Stacksync ships production-grade connectors for both DuckDB and IBM AS/400. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on DuckDB: Polling or full re-reads; no change feed or transaction log API. On IBM AS/400: Journal-based CDC by reading journal receivers on journaled files; polling as a fallback. 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 DuckDB and IBM AS/400.