Real-time
Two-way sync
Changes in InterSystems IRIS or Starburst Enterprise instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Data warehouse
InterSystems IRIS to Starburst Enterprise integration — real-time, two-way sync
Keep InterSystems IRIS 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.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect InterSystems IRIS and Starburst Enterprise
Connect InterSystems IRIS and Starburst Enterprise with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.
Operational databases and analytical warehouses want the same data at different moments. Analysts want InterSystems IRIS'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 InterSystems IRIS where the services that read from it get them at normal query latency.
Stacksync covers both directions with one connection. Tables or collections in InterSystems IRIS sync into Starburst Enterprise in real time, and result tables in Starburst Enterprise sync back into InterSystems IRIS, with schema and type mapping between the two systems handled for you.
Common use cases
- 01 Read federated views that join warehouse, lake, and database tables, then sync the result into operational tools like a CRM
- 02 Expose Iceberg or Hive lake tables to sync jobs through one SQL endpoint without moving the data first
- 03 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
- 04 Replicate IRIS tables to Postgres so application teams can build against a familiar database
Common sync patterns
Operational data in the warehouse, minus the pipeline
Rows from InterSystems IRIS land in Starburst Enterprise as they change, replacing hand-built CDC and batch extract jobs.
Serve warehouse results at database speed
Aggregates or model outputs computed in Starburst Enterprise sync into InterSystems IRIS, where whatever reads from that database gets them without querying the warehouse.
Fresh analytics without loading windows
Because changes stream continuously, analysts query current data instead of waiting for last night's load.
What you can sync between InterSystems IRIS and Starburst Enterprise
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.
| InterSystems IRIS objects | Starburst Enterprise objects | How this pairing syncs | |
|---|---|---|---|
| Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Tables Queryable relations; writes pass through to sources whose connectors support them. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Views SQL views expose curated slices of data for outbound replication. | 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. | |
| Schemas Schema organization scopes which tables a sync connection can see. | 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. | |
| Namespaces Namespaces partition databases and determine the connection context for integrations. | Materialized views Precomputed results that make repeated sync reads cheaper. | Namespaces is specific to InterSystems IRIS and Materialized views to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Columns Typed per the Trino type system, mapped from each source's native types. | Stored Procedures is specific to InterSystems IRIS and Columns to Starburst Enterprise — each maps to any object or custom field on the other side. | |
| Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. | Catalogs Each catalog maps to a connector (Iceberg, Hive, PostgreSQL, and others) exposing an external source. | Persistent Classes is specific to InterSystems IRIS and Catalogs to Starburst Enterprise — each maps to any object or custom field on the other side. |
How changes propagate between InterSystems IRIS and Starburst Enterprise
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.
InterSystems IRIS Starburst Enterprise Interval-based propagation
DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).
DeliveryEach detected change is applied to Starburst Enterprise as a row-level write, with types converted between the two schemas.
Starburst Enterprise InterSystems IRIS Interval-based propagation
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 InterSystems IRIS as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
- Starburst Enterprise: Throughput is governed by cluster sizing and resource groups rather than API quotas.
What ships with InterSystems IRIS ⇄ Starburst Enterprise
Connect InterSystems IRIS and Starburst Enterprise for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every InterSystems IRIS–Starburst Enterprise connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever InterSystems IRIS or Starburst Enterprise data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single InterSystems IRIS or Starburst Enterprise record.
Observability
Monitoring
Track your InterSystems IRIS ⇄ Starburst Enterprise sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between InterSystems IRIS and Starburst Enterprise.
How the InterSystems IRIS and Starburst Enterprise connectors work
InterSystems IRIS
- Integration surface
- SQL over JDBC/ODBC, plus object and REST access layers
- Authentication
- Database credentials
- Change detection
- Polling (timestamp or query-based); no standard webhook surface
- Capabilities
- read · write
- Rate limits
- Constrained by database resources rather than published API rate limits
Starburst Enterprise
- Integration surface
- ANSI SQL over JDBC/ODBC drivers and the Trino client REST protocol
- Authentication
- Deployment-dependent: username/password, LDAP, OAuth 2.0, or Kerberos
- Change detection
- Query-based polling; Starburst is a query engine and exposes no change log of its own
- Capabilities
- read · write
- Rate limits
- Throughput is governed by cluster sizing and resource groups rather than API quotas
How it works
How to connect InterSystems IRIS to Starburst Enterprise — three steps, no code
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.
- 01
Connect your apps
Authenticate InterSystems IRIS 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.
InterSystems IRIS
connected
Starburst Enterprise
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the InterSystems IRIS 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.
objects · InterSystems IRIS ⇄ Starburst EnterpriseCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
InterSystems IRIS Starburst EnterpriseCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
InterSystems IRIS and Starburst Enterprise integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between InterSystems IRIS and Starburst Enterprise: authenticate both systems, choose the objects to sync (such as InterSystems IRIS's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. 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: It is built on open-source Trino, so Trino drivers, clients, and SQL semantics apply. InterSystems IRIS: Standard JDBC and ODBC drivers are available, which lets IRIS participate in database-style sync pipelines without a vendor-specific client. Stacksync's field mapping accounts for these differences between InterSystems IRIS 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 InterSystems IRIS 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 InterSystems IRIS and Starburst Enterprise connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom InterSystems IRIS–Starburst Enterprise integration in-house.
-
Yes — Stacksync ships production-grade connectors for both InterSystems IRIS and Starburst Enterprise. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
SECURITY
Security teams trust Stacksync
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 399 integrations available for InterSystems IRIS and Starburst Enterprise.
Popular · 3 of 399
-
InterSystems IRIS ⇄ Amazon Redshift -
InterSystems IRIS ⇄ Apache Druid -
Starburst Enterprise ⇄ PostgreSQL
No integrations match .
