Skip to content
Developer tools ⇄ Database

Azure Service Bus to MarkLogic integration — real-time, two-way sync

Keep Azure Service Bus and MarkLogic 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 MarkLogic

Keep MarkLogic and Azure Service Bus in step: the rows in your database and the Queues, Topics, Subscriptions, Messages your engineering tools track stay consistent in real time, in both directions.

MarkLogic 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 Semantic Triples, TDE Views, Document Metadata & Properties, Databases & Forests in MarkLogic with Queues, Topics, Subscriptions, Messages 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 Land document data in relational warehouses by reading TDE views as SQL rows.
  • 02 Write updates from operational systems back into the document hub to keep the canonical record current.
  • 03 Send new and changed database rows as messages to a Service Bus queue or topic so multiple downstream consumers process the change stream independently.
  • 04 Receive messages from a queue or subscription with an AMQP receiver and write them into a Postgres or warehouse table for durable, SQL-queryable storage.

Common sync patterns

Land tool activity as queryable rows

Records and events from Azure Service Bus arrive in MarkLogic as rows, so tickets, alerts, messages, or identity changes become joinable data your services and reports read directly.

One integration pattern instead of per-tool API code

Read and write the synced tables in MarkLogic and Stacksync keeps Azure Service Bus current, replacing the auth, webhooks, rate limits, and retry logic you would otherwise maintain for each tool.

React to changes on either side in near real time

Updates in Azure Service Bus arrive as row changes in MarkLogic, and writes to MarkLogic propagate to Azure Service Bus within seconds, so triggers, jobs, and alerts fire without polling.

What you can sync between Azure Service Bus and MarkLogic

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 MarkLogic objects How this pairing syncs
Rules / Filters SQL or correlation filters on a subscription that decide which topic messages it receives; a rule can also add or modify properties via a filter action. Semantic Triples RDF data stored alongside documents, queryable with SPARQL for linked-data syncs. Rules / Filters is specific to Azure Service Bus and Semantic Triples to MarkLogic — each maps to any object or custom field on the other side.
Sessions Message sessions group related messages by SessionId so one consumer handles them in FIFO order; the way ordered processing is achieved in Service Bus. TDE Views Relational projections of documents that let syncs read document data as SQL rows. Sessions is specific to Azure Service Bus and TDE Views to MarkLogic — each maps to any object or custom field on the other side.
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. Document Metadata & Properties Permissions, quality, and property fragments carried with each document. Dead-letter queue is specific to Azure Service Bus and Document Metadata & Properties to MarkLogic — 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. Databases & Forests Storage units that define the scope and placement of synced content. Scheduled / deferred messages is specific to Azure Service Bus and Databases & Forests to MarkLogic — 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. Users & Roles Security principals that govern what an integration credential can read or write. Queues is specific to Azure Service Bus and Users & Roles to MarkLogic — 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. Documents JSON and XML documents, the primary records read from and written to the database. Topics is specific to Azure Service Bus and Documents to MarkLogic — each maps to any object or custom field on the other side.

How changes propagate between Azure Service Bus and MarkLogic

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 MarkLogic 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 MarkLogic as a row-level write, with types converted between the two schemas.

MarkLogic Azure Service Bus Interval-based propagation

DetectionStacksync polls MarkLogic for changes on an incremental schedule, reading only records changed since the previous pass. No exposed transaction log.

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.
What ships with Azure Service Bus ⇄ MarkLogic

Connect Azure Service Bus and MarkLogic for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Service Bus–MarkLogic connection.

Real-time

Two-way sync

Changes in Azure Service Bus or MarkLogic instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Service Bus or MarkLogic 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 MarkLogic record.

Observability

Monitoring

Track your Azure Service Bus ⇄ MarkLogic 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 MarkLogic.

How the Azure Service Bus and MarkLogic 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

MarkLogic

Integration surface
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
Change detection
No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup
Capabilities
read · write
How it works

How to connect Azure Service Bus to MarkLogic — 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.

  1. 01

    Connect your apps

    Authenticate Azure Service Bus and MarkLogic with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Azure Service Bus connected
    MarkLogic connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Service Bus and MarkLogic 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Azure Service Bus ⇄ MarkLogic
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Azure Service Bus MarkLogic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Azure Service Bus and MarkLogic integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 317 integrations available for Azure Service Bus and MarkLogic.

Popular · 7 of 317
All Azure Service Bus integrations All MarkLogic integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own