Two-way sync
Changes in MarkLogic or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Keep MarkLogic 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 MarkLogic'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 MarkLogic where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in MarkLogic sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into MarkLogic, with schema and type mapping between the two systems handled for you.
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
Point analytical queries at the synced copy in Starburst Enterprise and keep MarkLogic focused on its operational workload.
Rows from MarkLogic land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
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.
| MarkLogic objects | Starburst Enterprise objects | |
|---|---|---|
| Users & Roles Security principals that govern what an integration credential can read or write. | Columns Typed per the Trino type system, mapped from each source's native types. | |
| Documents JSON and XML documents, the primary records read from and written to the database. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | |
| Collections Named groupings used to scope which documents a sync reads or updates. | Schemas Namespaces within a catalog, mirroring the underlying source's databases or schemas. | |
| Semantic Triples RDF data stored alongside documents, queryable with SPARQL for linked-data syncs. | Tables Queryable relations; writes pass through to sources whose connectors support them. | |
| TDE Views Relational projections of documents that let syncs read document data as SQL rows. | Views Engine-level SQL views used to shape federated data before syncing it out. | |
| Document Metadata & Properties Permissions, quality, and property fragments carried with each document. | Materialized views Precomputed results that make repeated sync reads cheaper. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MarkLogic–Starburst Enterprise connection.
Changes in MarkLogic or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever MarkLogic 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 MarkLogic or Starburst Enterprise record.
Track your MarkLogic ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between MarkLogic 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 MarkLogic 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 MarkLogic 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 MarkLogic and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as MarkLogic's Users & Roles and Documents), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on MarkLogic: No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup. 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 Starburst Enterprise side: Schemas, Tables, Views, Materialized views, plus custom fields where Starburst Enterprise exposes them. On the MarkLogic side: TDE Views, Document Metadata & Properties, Databases & Forests, Users & Roles. 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 MarkLogic and Starburst Enterprise: Fresh analytics without loading windows; Offload heavy reads; Operational data in the warehouse, minus the pipeline. Because changes stream continuously, analysts query current data instead of waiting for last night's load.
MarkLogic: REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries. Authentication: Username/password (digest or basic), with certificate-based options. 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.
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 MarkLogic and Starburst Enterprise.