Skip to content

Commit bca2957

Browse files
committed
second article
1 parent cd6d1e0 commit bca2957

1 file changed

Lines changed: 27 additions & 14 deletions

File tree

articles/event-grid/use-cases.md

Lines changed: 27 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,65 +1,75 @@
11
---
2-
title: Use cases for using Azure Event Grid
3-
description: This article provides a list of use cases that show you how to use both Message Queuing Telemetry Transport (MQTT) and HTTP messaging capabilities of Event Grid.
2+
title: Azure Event Grid Use Cases for Event-Driven Apps
3+
description: This article provides a list of use cases that show you how to use both Message Queuing Telemetry Transport (MQTT) and HTTP messaging capabilities of Event Grid.
44
ms.topic: concept-article
55
author: robece
66
ms.author: robece
7+
ms.reviewer: spelluru
78
ms.custom:
89
- references_regions
910
- build-2024
10-
ms.date: 02/04/2025
11+
ms.date: 03/26/2026
1112
# Customer intent: As an architect or a developer, I want to know what Azure Event Grid is and how it can help me with creating event-driven applications.
1213
---
1314

1415
# Azure Event Grid use cases
1516

16-
This article provides you with a few sample use cases for using Azure Event Grid.
17+
This article provides several sample use cases for using Azure Event Grid.
1718

1819
> [!NOTE]
19-
> If you are new to Azure Event Grid, read through the [Azure Event Grid overview](overview.md) article before proceeding further.
20+
> If you're new to Azure Event Grid, read the [Azure Event Grid overview](overview.md) before proceeding.
2021
2122
## MQTT messaging use cases
22-
Azure Event Grid’s MQTT broker feature enables you to accomplish the following scenarios.
23+
24+
Azure Event Grid's MQTT broker feature enables you to accomplish the following scenarios.
2325

2426
### Ingest IoT telemetry
27+
2528
:::image type="content" source="media/overview/ingest-telemetry.png" alt-text="High-level diagram of Event Grid that shows IoT clients using MQTT protocol to send messages to a cloud app." lightbox="media/overview/ingest-telemetry-high-res.png" border="false":::
2629

27-
Ingest telemetry using a **many-to-one messaging** pattern. For example, use Event Grid to send telemetry from multiple IoT devices to a cloud application. This pattern enables the application to offload the burden of managing the high number of connections with devices to Event Grid.
30+
Ingest telemetry by using a **many-to-one messaging** pattern. For example, use Event Grid to send telemetry from multiple IoT devices to a cloud application. This pattern enables the application to offload the burden of managing the high number of connections with devices to Event Grid.
2831

2932
### Command and control
33+
3034
:::image type="content" source="media/overview/command-control.png" alt-text="High-level diagram of Event Grid that shows a cloud application sending a command message over MQTT to a device using request and response topics." lightbox="media/overview/command-control-high-res.png" border="false":::
3135

32-
Control your MQTT clients using the **request-response** (one-to-one) message pattern. For example, use Event Grid to send a command from a cloud application to an IoT device.
36+
Control your MQTT clients by using the **request-response** (one-to-one) message pattern. For example, use Event Grid to send a command from a cloud application to an IoT device.
3337

3438
### Broadcast alerts
39+
3540
:::image type="content" source="media/overview/broadcast-alerts.png" alt-text="High-level diagram of Event Grid that shows a cloud application sending an alert message over MQTT to several devices." lightbox="media/overview/broadcast-alerts-high-res.png" border="false":::
3641

37-
Broadcast alerts to a fleet of clients using the **one-to-many** messaging pattern. For example, use Event Grid to send an alert from a cloud application to multiple IoT devices. This pattern enables the application to publish only one message that the service replicates for every interested client.
42+
Broadcast alerts to a fleet of clients by using the **one-to-many** messaging pattern. For example, use Event Grid to send an alert from a cloud application to multiple IoT devices. This pattern enables the application to publish only one message that the service replicates for every interested client.
3843

3944
### Integrate MQTT data
45+
4046
:::image type="content" source="media/overview/integrate-data.png" alt-text="Diagram that shows several IoT devices sending health data over MQTT to Event Grid." lightbox="media/overview/integrate-data-high-res.png" border="false":::
4147

4248
Integrate data from your MQTT clients by routing MQTT messages to Azure services and custom endpoints through [push delivery](overview.md#push-delivery) or [pull delivery](overview.md#pull-delivery). For example, use Event Grid to route telemetry from your IoT devices to Event Hubs and then to Azure Stream Analytics to gain insights from your device telemetry.
4349

4450
## Push delivery use cases
45-
Event Grid’s push delivery allows you to realize the following use cases.
51+
Event Grid push delivery enables the following use cases.
4652

4753
### Build event-driven serverless solutions
54+
4855
:::image type="content" source="media/overview/build-event-serverless.png" alt-text="Diagram that shows Azure Functions publishing events to Event Grid using HTTP. Event Grid then sends those events to Azure Logic Apps." lightbox="media/overview/build-event-serverless-high-res.png" border="false":::
4956

50-
Use Event Grid to build serverless solutions with Azure Functions Apps, Logic Apps, and API Management. Using serverless services with Event Grid affords you a level of productivity, effort economy, and integration superior to that of classical computing models where you have to procure, manage, secure, and maintain all infrastructure deployed.
57+
Use Event Grid to build serverless solutions with Azure Functions Apps, Logic Apps, and API Management. By using serverless services with Event Grid, you get a level of productivity, effort economy, and integration that's superior to classical computing models where you have to procure, manage, secure, and maintain all infrastructure deployed.
5158

5259
### Receive events from Azure services
60+
5361
:::image type="content" source="media/overview/receive-events-azure.png" alt-text="Diagram that shows Blob Storage publishing events to Event Grid over HTTP." lightbox="media/overview/receive-events-azure-high-res.png" border="false":::
5462

55-
Event Grid can receive events from 20+ Azure services so that you can automate your operations. For example, you can configure Event Grid to receive an event when a new blob has been created on an Azure Storage Account so that your downstream application can read and process its content. For a list of all supported Azure services and events, see [System topics](system-topics.md).
63+
Event Grid can receive events from more than 20 Azure services so that you can automate your operations. For example, you can configure Event Grid to receive an event when a new blob is created on an Azure Storage Account so that your downstream application can read and process its content. For a list of all supported Azure services and events, see [System topics](system-topics.md).
5664

5765
### Receive events from your applications
66+
5867
:::image type="content" source="media/overview/receive-events-apps.png" alt-text="Diagram that shows customer application publishing events to Event Grid using HTTP. Event Grid sends those events to webhooks or Azure services." lightbox="media/overview/receive-events-apps-high-res.png" border="false":::
5968

6069
Your own service or application publishes events to Event Grid that subscriber applications process. Event Grid features [Namespace Topics](concepts-event-grid-namespaces.md#namespace-topics) to address integration and routing requirements at scale with a simple resource model. You can also use [Custom Topics](custom-topics.md) to meet basic integration requirements and [Domains](event-domains.md) for a simple management and routing model when you need to distribute events to hundreds or thousands of different groups.
6170

6271
### Receive events from partner (SaaS providers)
72+
6373
:::image type="content" source="media/overview/receive-saas-providers.png" alt-text="Diagram that shows an external partner application publishing event to Event Grid using HTTP." lightbox="media/overview/receive-saas-providers-high-res.png" border="false":::
6474

6575
A multitenant SaaS provider or platform can publish their events to Event Grid through a feature called [Partner Events](partner-events-overview.md). You can [subscribe to those events](subscribe-to-partner-events.md) and automate tasks, for example. Events from the following partners are currently available:
@@ -69,14 +79,17 @@ A multitenant SaaS provider or platform can publish their events to Event Grid t
6979
- [Tribal Group](subscribe-to-tribal-group-events.md)
7080

7181
## Pull delivery use cases
72-
Azure Event Grid features [pull CloudEvents delivery](pull-delivery-overview.md#push-and-pull-delivery). With this delivery mode, clients connect to Event Grid to read events. The following use cases can be realized using pull delivery.
82+
83+
Azure Event Grid features [pull CloudEvents delivery](pull-delivery-overview.md#push-and-pull-delivery). By using this delivery mode, clients connect to Event Grid to read events. The following use cases can be realized by using pull delivery.
7384

7485
### Receive events at your own pace
86+
7587
:::image type="content" source="media/overview/pull-events-at-your-own-pace.png" alt-text="High-level diagram of a publisher and consumer application." lightbox="media/overview/pull-events-at-your-own-pace-high-res.png" border="false":::
7688

77-
One or more clients can connect to Azure Event Grid to read messages at their own pace. Event Grid affords clients full control on events consumption. Your application can receive events at certain times of the day, for example. Your solution can also increase the rate of consumption by adding more clients that read from Event Grid.
89+
One or more clients can connect to Azure Event Grid to read messages at their own pace. Event Grid gives clients full control over event consumption. Your application can receive events at certain times of the day, for example. Your solution can also increase the rate of consumption by adding more clients that read from Event Grid.
7890

7991
### Consume events over a private link
92+
8093
:::image type="content" source="media/overview/consume-private-link-pull-api.png" alt-text="High-level diagram of a consumer app inside a virtual network reading events from Event Grid over a private endpoint inside the virtual network." lightbox="media/overview/consume-private-link-pull-api-high-res.png" border="false":::
8194

8295
You can configure **private links** to connect to Azure Event Grid to **publish and read** CloudEvents through a [private endpoint](../private-link/private-endpoint-overview.md) in your virtual network. Traffic between your virtual network and Event Grid travels the Microsoft backbone network.

0 commit comments

Comments
 (0)