Skip to main content

Eventing Service Workload

Overview

An Eventing Service Workload represents a Platform-as-a-Service environment capable of supporting asynchronous event-driven architecture. Configuring this workload scaffolds the required governance and infrastructure-as-code to deploy an Azure Event Hub namespace[1], along with the additional resources required for it to run in your environment.

Architecture

Eventing Service Architecture

Capabilities

Add-ons

Diagnostic Logging

The Diagnostic Logging Add-on is automatically configured upon adding an Logging Link. This add-on enables diagnostic logging for cloud resources included with the workload and transmitted to the linked Log Analytics[2] workspace.

A Logging Link collects the necessary information from the linked Log Analytics workspace and triggers the provisioning of the Diagnostic Logging Add-on.

Ports

Eventing Port

An Eventing Port enables the connection of one or more Functional Workloads such as a Backend Service. Linking this port grants the identity of the linked workload, permission to send and receive events from the linked event broker. The environment variables for the linked service are automatically updated with the connection information required to send and receive messages from the broker.

Use Cases

  • Event-driven applications such as Kafka consumers

References