From 5df7af08f563febbf35025922086f3b2ea6f0c78 Mon Sep 17 00:00:00 2001 From: Josh van Leeuwen Date: Tue, 25 Jun 2024 14:14:53 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Mark Fussell Signed-off-by: Josh van Leeuwen --- .../building-blocks/pubsub/pubsub-overview.md | 6 +++--- .../building-blocks/pubsub/subscription-methods.md | 12 ++++++------ 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md index 0638d8c42..9916d2591 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-overview.md @@ -75,15 +75,15 @@ In principle, Dapr considers a message successfully delivered once the subscribe ### Receiving messages with topic subscriptions -Dapr applications can subscribe to published topics via three methods that support the same features: declarative, streaming and programmatic. +Dapr applications can subscribe to published topics via three subscription types that support the same features: declarative, streaming and programmatic. -| Subscription method | Description | +| Subscription type | Description | | ------------------- | ----------- | | **Declarative** | The subscription is defined in an **external file**. The declarative approach removes the Dapr dependency from your code and allows for existing applications to subscribe to topics, without having to change code. | | **Streaming** | The subscription is defined in the **user code**. Streaming subscriptions are dynamic, meaning they allow for adding or removing subscriptions at runtime. They do not require a subscription endpoint in your application (that is required by both programmatic and declarative subscriptions), making them easy to configure in code. Streaming subscriptions also do not require an app to be configured with the sidecar to receive messages. With streaming subscriptions, since messages are sent to a message handler code, there is no concept of routes or bulk subscriptions. | | **Programmatic** | Subscription is defined in the **user code**. The programmatic approach implements the static subscription and requires an endpoint in your code. | -For more information, read [about the subscriptions in Subscription Methods]({{< ref subscription-methods.md >}}). +For more information, read [about the subscriptions in Subscription Types]({{< ref subscription-methods.md >}}). ### Reloading topic subscriptions diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md index 52fc2059b..16fe5f88e 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md @@ -1,16 +1,16 @@ --- type: docs -title: "Declarative, streaming, and programmatic subscription methods" -linkTitle: "Subscription methods" +title: "Declarative, streaming, and programmatic subscription types" +linkTitle: "Subscription types" weight: 3000 -description: "Learn more about the methods by which Dapr allows you to subscribe to topics." +description: "Learn more about the subscription types that allow you to subscribe to message topics." --- -## Pub/sub API subscription methods +## Pub/sub API subscription types -Dapr applications can subscribe to published topics via three methods that support the same features: declarative, streaming and programmatic. +Dapr applications can subscribe to published topics via three subscription types that support the same features: declarative, streaming and programmatic. -| Subscription method | Description | +| Subscription type | Description | | ------------------- | ----------- | | [**Declarative**]({{< ref "subscription-methods.md#declarative-subscriptions" >}}) | Subscription is defined in an **external file**. The declarative approach removes the Dapr dependency from your code and allows for existing applications to subscribe to topics, without having to change code. | | [**Streaming**]({{< ref "subscription-methods.md#streaming-subscriptions" >}}) | Subscription is defined in the **application code**. Streaming subscriptions are dynamic, meaning they allow for adding or removing subscriptions at runtime. They do not require a subscription endpoint in your application (that is required by both programmatic and declarative subscriptions), making them easy to configure in code. Streaming subscriptions also do not require an app to be configured with the sidecar to receive messages. |