Two-way sync
Changes in OCI Database (Oracle Cloud) or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep OCI Database (Oracle Cloud) and Starburst Enterprise in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Operational databases and analytical warehouses want the same data at different moments. Analysts want OCI Database (Oracle Cloud)'s rows in Starburst Enterprise, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in OCI Database (Oracle Cloud) where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in OCI Database (Oracle Cloud) sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into OCI Database (Oracle Cloud), with schema and type mapping between the two systems handled for you.
Rows from OCI Database (Oracle Cloud) land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
Aggregates or model outputs computed in Starburst Enterprise sync into OCI Database (Oracle Cloud), where whatever reads from that database gets them without querying the warehouse.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
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.
| OCI Database (Oracle Cloud) objects | Starburst Enterprise objects | |
|---|---|---|
| Sequences Key generators that matter when writing new rows from external systems | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| JSON collections Document-style storage in the converged engine, synced alongside relational tables | Materialized views Precomputed results that make repeated sync reads cheaper. | |
| Partitions Physical table subdivisions relevant when replicating large fact tables | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Tables The primary sync surface; rows are read and written directly over SQL | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Views Read-only projections used to expose curated subsets to downstream systems | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–Starburst Enterprise connection.
Changes in OCI Database (Oracle Cloud) or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever OCI Database (Oracle Cloud) or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single OCI Database (Oracle Cloud) or Starburst Enterprise record.
Track your OCI Database (Oracle Cloud) ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) and Starburst Enterprise.
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 OCI Database (Oracle Cloud) and Starburst Enterprise 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 OCI Database (Oracle Cloud) and Starburst Enterprise 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 OCI Database (Oracle Cloud) and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as OCI Database (Oracle Cloud)'s Sequences and PL/SQL procedures and packages), map fields visually, and changes propagate both ways in milliseconds — no code required.
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. Starburst Enterprise: ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol. Authentication: Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos. Stacksync manages authentication, retries, and rate limits on both sides.
Starburst Enterprise: A single SQL statement can join tables across catalogs, meaning one query can span several distinct backend systems. OCI Database (Oracle Cloud): The converged data model holds relational, JSON, spatial, and graph data in one engine, so a single connection can cover mixed workloads. Stacksync's field mapping accounts for these differences between OCI Database (Oracle Cloud) and Starburst Enterprise 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 OCI Database (Oracle Cloud) and Starburst Enterprise records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed OCI Database (Oracle Cloud) and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom OCI Database (Oracle Cloud)–Starburst Enterprise integration in-house.
Yes — Stacksync ships production-grade connectors for both OCI Database (Oracle Cloud) and Starburst Enterprise. 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:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for OCI Database (Oracle Cloud) and Starburst Enterprise.