Skip to content

Commit fbda01a

Browse files
committed
update introductions
Signed-off-by: Ryan Winter <[email protected]>
1 parent f59a483 commit fbda01a

File tree

2 files changed

+4
-11
lines changed

2 files changed

+4
-11
lines changed

articles/iot-operations/develop/howto-develop-deploy-dapr.md renamed to articles/iot-operations/develop/howto-deploy-dapr.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,10 @@ The Distributed Application Runtime (Dapr) is a portable, serverless, event-driv
1818

1919
Azure IoT MQ Preview supports two of these building blocks, powered by [Azure IoT MQ MQTT broker](../manage-mqtt-connectivity/overview-iot-mq.md):
2020

21-
- Pub/sub
21+
- Publish and Subscribe
2222
- State Management
2323

24-
To use Dapr pluggable components, register the components, then add the pluggable component containers to your [deployments](https://docs.dapr.io/operations/components/pluggable-components-registration/). The Dapr component listens to a Unix Domain Socket placed on the shared volume, and Dapr runtime connects with each socket and discovers all services from a given building block API that the component implements.
25-
26-
This guide shows you how to deploy an application using the Dapr SDK and IoT MQ pluggable components.
24+
To use the IoT MQ Dapr pluggable components, define the component spec for each of the APIs and then [register this to the cluster](https://docs.dapr.io/operations/components/pluggable-components-registration/). The Dapr components listen to a Unix Domain Socket placed on the shared volume, and Dapr runtime connects with each socket and discovers all services from a given building block API that the component implements.
2725

2826
## Install Dapr runtime
2927

articles/iot-operations/develop/howto-develop-dapr-apps.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,14 @@ ms.custom:
1010
- ignite-2023
1111
ms.date: 11/14/2023
1212

13-
# CustomerIntent: As an developer, I want to understand how to use Dapr to develop distributed apps that talk with Azure IoT MQ.
13+
# CustomerIntent: As a developer, I want to understand how to use Dapr to develop distributed apps that talk with Azure IoT MQ.
1414
---
1515

1616
# Use Dapr to develop distributed application workloads
1717

1818
[!INCLUDE [public-preview-note](../includes/public-preview-note.md)]
1919

20-
The Distributed Application Runtime (Dapr) is a portable, serverless, event-driven runtime that simplifies the process of building distributed application. Dapr enables developers to build stateful or stateless apps without worrying about how the building blocks function. Dapr provides several [building blocks](https://docs.dapr.io/developing-applications/building-blocks/): state management, service invocation, actors, pub/sub, and more. Azure IoT MQ Preview supports two of these building blocks:
21-
22-
- Publish and Subscribe, powered by [Azure IoT MQ MQTT broker](../manage-mqtt-connectivity/overview-iot-mq.md)
23-
- State Management
24-
25-
To use Dapr pluggable components, define all the components, then add pluggable component containers to your [deployments](https://docs.dapr.io/operations/components/pluggable-components-registration/). The Dapr component listens to a Unix Domain Socket placed on the shared volume, and Dapr runtime connects with each socket and discovers all services from a given building block API that the component implements. Each deployment must have its own pluggable component defined. This guide shows you how to deploy an application using the Dapr SDK and IoT MQ pluggable components.
20+
To use the IoT MQ Dapr pluggable components, deploy both the pub/sub and state store components in your application deployment along with your Dapr application. This guide shows you how to deploy an application using the Dapr SDK and IoT MQ pluggable components.
2621

2722
## Prerequisites
2823

0 commit comments

Comments
 (0)