Two-way sync
Changes in CockroachDB or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Keep CockroachDB 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 CockroachDB 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.
Keep the same dataset live in both CockroachDB 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.
Services that own separate databases stay consistent on the records they share, without a custom replication layer.
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.
| CockroachDB objects | OCI Database (Oracle Cloud) objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces within a database used to isolate synced tables from application tables. | 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 The core read/write target; rows sync bi-directionally with SaaS objects or other databases. | 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 Read-only projections used as curated sync sources. | 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. | |
| Sequences ID generators that matter when writes originate from an external system. | Sequences Key generators that matter when writing new rows from external systems | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Changefeeds Built-in CDC streams that emit row-level changes to external sinks. | PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Changefeeds is specific to CockroachDB and PL/SQL procedures and packages to OCI Database (Oracle Cloud) — each maps to any object or custom field on the other side. | |
| Databases Logical containers a sync connects to, addressed like PostgreSQL databases. | JSON collections Document-style storage in the converged engine, synced alongside relational tables | Databases is specific to CockroachDB and JSON collections 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.
DetectionChanges in CockroachDB are captured at the source via change data capture — no polling loop against its API. CDC via changefeeds, which stream row-level changes.
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 CockroachDB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every CockroachDB–OCI Database (Oracle Cloud) connection.
Changes in CockroachDB or OCI Database (Oracle Cloud) instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever CockroachDB 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 CockroachDB or OCI Database (Oracle Cloud) record.
Track your CockroachDB ⇄ OCI Database (Oracle Cloud) sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between CockroachDB 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 CockroachDB 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 CockroachDB 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 CockroachDB and OCI Database (Oracle Cloud): authenticate both systems, choose the objects to sync (such as CockroachDB's Schemas and Tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
CockroachDB: SQL wire protocol (PostgreSQL-compatible). Authentication: Database credentials with TLS; client certificates or SCRAM password auth. 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.
CockroachDB: CockroachDB speaks the PostgreSQL wire protocol, so standard Postgres drivers and tooling connect without modification. OCI Database (Oracle Cloud): OCI database services run the same Oracle Database engine as on-premises installs, so PL/SQL, sequences, and redo-log CDC behave identically to self-managed Oracle. Stacksync's field mapping accounts for these differences between CockroachDB and OCI Database (Oracle Cloud) 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 CockroachDB 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 CockroachDB and OCI Database (Oracle Cloud) connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom CockroachDB–OCI Database (Oracle Cloud) integration in-house.
Yes — Stacksync ships production-grade connectors for both CockroachDB and OCI Database (Oracle Cloud). The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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: