Real-Time Analytics Platform  ·  View 05 of 21  ·  Structure

Integration and Interface Catalogue

Every way the platform touches another system, with protocol, direction and cadence — the single page an enterprise architect can review against the estate.

Editable source SVG draw.io All views
Inbound producers
Inbound producers
Web & Mobile SDK
Web & Mobile SDK
Partner Services
Partner Services
Devices & Edge
Devices & Edge
Azure SQL Database
Azure SQL Database
Kafka Estate
Kafka Estate
Batch File Drops
Batch File Drops
Platform
Platform
API Management
every inbound interface
API Management...
Azure Event Hubs
durable event log
Azure Event Hubs...
Azure Data Explorer
hot analytics store
Azure Data Explorer...
Outbound consumers
Outbound consumers
Power BI
Power BI
Managed Grafana
Managed Grafana
Downstream Apps
Downstream Apps
Logic Apps
Logic Apps
Microsoft Fabric
Microsoft Fabric
Azure Machine Learning
Azure Machine Learning
HTTPS batch
HTTPS batch
REST · OAuth2
REST · OAuth2
MQTT · AMQP
MQTT · AMQP
CDC · Debezium
CDC · Debezium
MirrorMaker 2
MirrorMaker 2
SFTP to ADLS
SFTP to ADLS
DirectQuery
DirectQuery
ADX data source
ADX data source
gold topics
gold topics
threshold events
threshold events
continuous export
continuous export
Delta share
Delta share
Integration and Interface Catalogue
Integration and Interface Catalogue
External / third party
External / third party
Interface / broker
Interface / broker
Queue / topic
Queue / topic
Data store
Data store
event / async
event / async
synchronous
synchronous
batch
batch
Every inbound interface authenticates with Entra ID; no shared keys are issued to producers.
Every inbound interface authenticates with Entra ID; no shared keys are issued to producers.
v 1.0 · owner Integration Architecture · date 2026-08
v 1.0 · owner Integration Architecture · date 2026-08Text is not SVG - cannot display

Interface rules

  • Inbound interfaces authenticate with Entra ID; producers never hold a shared access key
  • Every inbound payload carries an event_id and a registered schema ID, or it is rejected
  • Outbound contracts are versioned; a consumer pins a schema ID, not a topic name

Ownership

  • The platform owns the collector API, the topics and the query surface
  • Producers own their SDK version, their schema and their retry behaviour
  • The CDC connector is jointly owned: platform runs it, the source team approves the tables

Open questions

  • MirrorMaker 2 from the existing Kafka estate assumes network peering that is not yet in place
  • SFTP file drops are a transitional interface with no agreed sunset date
  • Partner rate limits are provisional until real traffic shapes are observed
◀  Container Architecture All views Tenancy and Workload Isolation  ▶
Solution Architecture v1.0 · Azure · Data & AI Architecture · 2026-0805-integration-catalogue