Two-way sync
Changes in Databricks or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep Databricks 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.
Companies end up with two warehouses for practical reasons: a migration in progress, teams that standardized on different platforms, an acquisition, or tools that only connect to one of them. The result is the same dataset maintained twice, with duplicated pipelines and numbers that almost match.
Stacksync syncs tables between Databricks and Starburst Enterprise continuously, in either or both directions. Rows changed on one platform appear on the other within seconds, with schema and type mapping handled, so both warehouses answer questions with the same data.
When one platform is replacing the other, keep tables mirrored while workloads move over gradually, and cut over with nothing to backfill.
Mirror the datasets a BI tool, notebook, or application needs onto the platform it can actually reach.
Where different teams run different warehouses, sync the curated tables both rely on so their metrics agree by construction.
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.
| Databricks objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Schemas Group tables and views; syncs typically target a dedicated schema per source system. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views Curated read-only projections used as sync sources for downstream tools. | Views Engine-level SQL views used to shape federated data before syncing it out. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. | Materialized views Precomputed results that make repeated sync reads cheaper. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Delta Tables The primary read and write target; operational data lands here as managed or external tables. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Delta Tables is specific to Databricks and Tables to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Volumes Unity Catalog file storage used for staging bulk loads. | Columns Typed per the Trino type system, mapped from each source's native types. | Volumes is specific to Databricks and Columns to Starburst Enterprise — 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 Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Starburst Enterprise for changes on an incremental schedule, reading only records changed since the previous pass. Query-based polling.
DeliveryEach detected change is applied to Databricks as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Databricks–Starburst Enterprise connection.
Changes in Databricks or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Databricks 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 Databricks or Starburst Enterprise record.
Track your Databricks ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Databricks 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 Databricks 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 Databricks 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 Databricks and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as Databricks's Catalogs and Schemas), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Databricks and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Databricks–Starburst Enterprise integration in-house.
Yes — Stacksync ships production-grade connectors for both Databricks and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Databricks: Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns. On Starburst Enterprise: Query-based polling; Starburst is a query engine and exposes no change log of its own. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Databricks side: Delta Tables, Views, Materialized Views, Volumes, plus custom fields where Databricks exposes them. On the Starburst Enterprise side: Materialized views, Columns, Catalogs, Schemas. 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.
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 480 integrations available for Databricks and Starburst Enterprise.