Two-way sync
Changes in DuckDB or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Keep DuckDB and OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud), 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 | OCI Database (Oracle Cloud) objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces within a database used to organize tables in sync outputs. | Schemas Namespace boundaries that scope which objects a sync connection can access | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tables Columnar tables created via SQL; the destination for materialized sync data. | Tables The primary sync surface; rows are read and written directly over SQL | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views SQL views used to shape or filter data for downstream consumers. | Views Read-only projections used to expose curated subsets to downstream systems | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Partitions Physical table subdivisions relevant when replicating large fact tables | External files (Parquet/CSV/JSON) is specific to DuckDB and Partitions to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| Attached databases Additional database files or external systems attached into one session for cross-source queries. | Materialized views Precomputed result sets sometimes used as stable read sources for replication | Attached databases is specific to DuckDB and Materialized views to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Sequences Key generators that matter when writing new rows from external systems | Database files is specific to DuckDB and Sequences to OCI Database (Oracle Cloud) — 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.
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
DeliveryEach detected change is applied to OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.
DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.
DeliveryEach detected change is applied to DuckDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DuckDB–OCI Database (Oracle Cloud) connection.
Changes in DuckDB or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DuckDB or OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) record.
Track your DuckDB ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DuckDB and OCI Database (Oracle Cloud).
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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud): 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.
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 OCI Database (Oracle Cloud) records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DuckDB and OCI Database (Oracle Cloud) connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DuckDB–OCI Database (Oracle Cloud) integration in-house.
Yes — Stacksync ships production-grade connectors for both DuckDB and OCI Database (Oracle Cloud). 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 OCI Database (Oracle Cloud): Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the DuckDB side: Database files, Schemas, Tables, Views, plus custom fields where DuckDB exposes them. On the OCI Database (Oracle Cloud) side: Partitions, Tables, Views, Materialized views. Stacksync auto-detects both schemas and converts types between the two systems.
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 378 integrations available for DuckDB and OCI Database (Oracle Cloud).