Real-time
Two-way sync
Changes in Azure Service Bus or InterSystems IRIS instantly reflect in both systems. No stale data, no manual imports.
Developer tools ⇄ Database
Azure Service Bus to InterSystems IRIS integration — real-time, two-way sync
Keep Azure Service Bus and InterSystems IRIS 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 Azure Service Bus and InterSystems IRIS
Keep InterSystems IRIS and Azure Service Bus in step: the rows in your database and the Topics, Subscriptions, Messages, Rules / Filters your engineering tools track stay consistent in real time, in both directions.
InterSystems IRIS is where your application's durable data lives; Azure Service Bus is where engineering and operations teams track the issues, events, messages, or identities that run alongside it. The two overlap constantly, a row should open a ticket, an alert should land as a record, a user in one should exist in the other, but bridging them today means per-tool integration code: auth, webhooks, pagination, rate limits, and retries, built and maintained separately for every tool.
Stacksync syncs Schemas, Persistent Classes, Globals, Namespaces in InterSystems IRIS with Topics, Subscriptions, Messages, Rules / Filters in Azure Service Bus field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set, so the database and the tooling around it never drift apart.
Common use cases
- 01 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
- 02 Replicate IRIS tables to Postgres so application teams can build against a familiar database
- 03 Preserve per-account or per-order processing order by grouping related messages into a session so a single consumer handles them in FIFO sequence.
- 04 Send new and changed database rows as messages to a Service Bus queue or topic so multiple downstream consumers process the change stream independently.
Common sync patterns
Where Azure Service Bus manages users or groups: keep identity aligned
Directory and identity records in Azure Service Bus stay matched to the users or owners table in InterSystems IRIS, so provisioning and de-provisioning flow from one source.
Turn rows into the records your tools track
A new or changed row in InterSystems IRIS creates or updates the matching record in Azure Service Bus, whether that is an issue, an event, a message, or a user, so the tool reflects the database without a custom API job.
Land tool activity as queryable rows
Records and events from Azure Service Bus arrive in InterSystems IRIS as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.
What you can sync between Azure Service Bus and InterSystems IRIS
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.
| Azure Service Bus objects | InterSystems IRIS objects | How this pairing syncs | |
|---|---|---|---|
| Dead-letter queue A sub-queue on every queue and subscription that automatically holds messages exceeding the max delivery count or their TTL, read for inspection and reprocessing. | Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. | Dead-letter queue is specific to Azure Service Bus and Globals to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Scheduled / deferred messages Messages enqueued for future delivery at a set time, or deferred and set aside by sequence number for retrieval later, out of the normal receive order. | Namespaces Namespaces partition databases and determine the connection context for integrations. | Scheduled / deferred messages is specific to Azure Service Bus and Namespaces to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Queues Point-to-point entity: a sender writes messages and one competing consumer at a time receives them under PeekLock, then completes or abandons each message. | Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. | Queues is specific to Azure Service Bus and Stored Procedures to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Topics Publish/subscribe entity a publisher sends to; each message is fanned out to every subscription whose filter rules match, so many consumers get their own copy. | Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. | Topics is specific to Azure Service Bus and Tables to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Subscriptions A virtual queue attached to a topic; a consumer receives its own stream of matching messages here, independent of other subscriptions on the same topic. | Views SQL views expose curated slices of data for outbound replication. | Subscriptions is specific to Azure Service Bus and Views to InterSystems IRIS — each maps to any object or custom field on the other side. | |
| Messages The synced unit: a body plus system and user properties, MessageId, SessionId, and TTL; capped at 256 KB on Standard and up to 100 MB on Premium over AMQP. | Schemas Schema organization scopes which tables a sync connection can see. | Messages is specific to Azure Service Bus and Schemas to InterSystems IRIS — each maps to any object or custom field on the other side. |
How changes propagate between Azure Service Bus and InterSystems IRIS
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.
Azure Service Bus InterSystems IRIS Interval-based propagation
DetectionStacksync polls Azure Service Bus for changes on an incremental schedule, reading only records changed since the previous pass. Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or.
DeliveryEach detected change is applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.
InterSystems IRIS Azure Service Bus 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 written to Azure Service Bus through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Azure Service Bus: Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity.
- InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Azure Service Bus ⇄ InterSystems IRIS
Connect Azure Service Bus and InterSystems IRIS for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Service Bus–InterSystems IRIS connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Service Bus or InterSystems IRIS 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 Azure Service Bus or InterSystems IRIS record.
Observability
Monitoring
Track your Azure Service Bus ⇄ InterSystems IRIS sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Azure Service Bus and InterSystems IRIS.
How the Azure Service Bus and InterSystems IRIS connectors work
Azure Service Bus
- Integration surface
- AMQP 1.0 messaging protocol plus an HTTP/REST API; entities live under a namespace at <namespace>.servicebus.windows.net (legacy SBMP also supported)
- Authentication
- Microsoft Entra ID (Azure AD) RBAC with managed identities - roles Azure Service Bus Data Owner, Data Sender, and Data Receiver - or Shared Access Signature (SAS) policies scoped with Manage, Send, and Listen claims
- Change detection
- Consumes messages as they arrive: an AMQP receiver holds an open connection and takes messages with PeekLock (lock, then complete/abandon) or ReceiveAndDelete. No modified-date polling and no native HTTP push; Azure Event Grid can separately raise an 'active messages available' event for intermittent receivers
- Capabilities
- read · write
- Rate limits
- Standard tier throttles around 1,000 operations/second and returns a ServerBusy error; Premium provisions dedicated messaging units (1, 2, 4, 8, or 16) for isolated, predictable throughput. Up to 5,000 concurrent AMQP connections per namespace and 5,000 concurrent receive requests per entity
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
How it works
How to connect Azure Service Bus to InterSystems IRIS — 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 Azure Service Bus and InterSystems IRIS with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Azure Service Bus
connected
InterSystems IRIS
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Service Bus and InterSystems IRIS 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 · Azure Service Bus ⇄ InterSystems IRISCustomers 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.
Azure Service Bus InterSystems IRISCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Service Bus and InterSystems IRIS integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Service Bus and InterSystems IRIS: authenticate both systems, choose the objects to sync (such as Azure Service Bus's Dead-letter queue and Scheduled / deferred messages), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Azure Service Bus and InterSystems IRIS: Where Azure Service Bus manages users or groups: keep identity aligned; Turn rows into the records your tools track; Land tool activity as queryable rows. Directory and identity records in Azure Service Bus stay matched to the users or owners table in InterSystems IRIS, so provisioning and de-provisioning flow from one source.
-
Azure Service Bus: AMQP 1.0 messaging protocol plus an HTTP/REST API; entities live under a namespace at <namespace>.servicebus.windows.net (legacy SBMP also supported). Authentication: Microsoft Entra ID (Azure AD) RBAC with managed identities - roles Azure Service Bus Data Owner, Data Sender, and Data Receiver - or Shared Access Signature (SAS) policies scoped with Manage, Send, and Listen claims. InterSystems IRIS: SQL over JDBC/ODBC, plus object and REST access layers. Authentication: Database credentials. Stacksync manages authentication, retries, and rate limits on both sides.
-
InterSystems IRIS: Standard JDBC and ODBC drivers are available, which lets IRIS participate in database-style sync pipelines without a vendor-specific client. Azure Service Bus: Delivery is at-least-once under PeekLock: a message stays locked while being processed and is redelivered if it is not completed before the lock expires, so consumers should be idempotent or use duplicate detection (dedupe by MessageId). Stacksync's field mapping accounts for these differences between Azure Service Bus and InterSystems IRIS 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 Azure Service Bus and InterSystems IRIS records are not retained after a sync operation.
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
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 346 integrations available for Azure Service Bus and InterSystems IRIS.
Popular · 8 of 346
-
Azure Service Bus ⇄ Supabase -
Azure Service Bus ⇄ MySQL -
Azure Service Bus ⇄ MariaDB -
Azure Service Bus ⇄ SQL Server -
InterSystems IRIS ⇄ PagerDuty -
InterSystems IRIS ⇄ Jira -
InterSystems IRIS ⇄ Rabbitmq -
InterSystems IRIS ⇄ Datadog
No integrations match .
