Two-way sync
Changes in Citus or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Keep Citus 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 Citus 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.
When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
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.
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.
| Citus objects | OCI Database (Oracle Cloud) objects | |
|---|---|---|
| Views Curated projections over distributed data, often used as read-only sync sources. | Sequences Key generators that matter when writing new rows from external systems | |
| Sequences Key generators that matter when external writes must not collide with application inserts. | PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | |
| Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. | JSON collections Document-style storage in the converged engine, synced alongside relational tables | |
| Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. | Partitions Physical table subdivisions relevant when replicating large fact tables | |
| Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. | Tables The primary sync surface; rows are read and written directly over SQL | |
| Schemas Standard Postgres namespaces used to scope what a sync user can read and write. | Views Read-only projections used to expose curated subsets to downstream systems |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–OCI Database (Oracle Cloud) connection.
Changes in Citus or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Citus 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 Citus or OCI Database (Oracle Cloud) record.
Track your Citus ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Citus 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 Citus 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 Citus 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 Citus and OCI Database (Oracle Cloud): authenticate both systems, choose the objects to sync (such as Citus's Views and Sequences), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Citus: PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres. 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 Citus side: Reference tables, Local tables, Schemas, Views, plus custom fields where Citus exposes them. On the OCI Database (Oracle Cloud) side: Materialized views, Schemas, Sequences, PL/SQL procedures and packages. 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 Citus and OCI Database (Oracle Cloud): Migration with zero-downtime cutover; Shared reference data between services; Regional or environment copies. When one database is replacing the other, sync both directions during the transition and switch traffic when ready, without a freeze window.
Citus: PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node. Authentication: Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options). OCI Database (Oracle Cloud): SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP. Authentication: Database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available. 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 386 integrations available for Citus and OCI Database (Oracle Cloud).