mirror of https://github.com/dapr/quickstarts.git
Updated readmes with cross pointers SDK <--> HTTP
This commit is contained in:
parent
49f3bddd1f
commit
a14374c633
|
|
@ -1,9 +1,11 @@
|
|||
# Dapr pub/sub
|
||||
# Dapr pub/sub (HTTP Client)
|
||||
|
||||
In this quickstart, you'll create a publisher microservice and a subscriber microservice to demonstrate how Dapr enables a publish-subcribe pattern. The publisher will generate messages of a specific topic, while subscribers will listen for messages of specific topics. See [Why Pub-Sub](#why-pub-sub) to understand when this pattern might be a good choice for your software architecture.
|
||||
|
||||
Visit [this](https://docs.dapr.io/developing-applications/building-blocks/pubsub/) link for more information about Dapr and Pub-Sub.
|
||||
|
||||
> **Note:** This example leverages HTTPClient only. If you are looking for the example using the Dapr Client SDK (recommended) [click here](../csharp/).
|
||||
|
||||
This quickstart includes one publisher:
|
||||
|
||||
- Dotnet client message generator `checkout`
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
# Dapr pub/sub (HTTP client)
|
||||
# Dapr pub/sub
|
||||
|
||||
In this quickstart, you'll create a publisher microservice and a subscriber microservice to demonstrate how Dapr enables a publish-subcribe pattern. The publisher will generate messages of a specific topic, while subscribers will listen for messages of specific topics. See [Why Pub-Sub](#why-pub-sub) to understand when this pattern might be a good choice for your software architecture.
|
||||
|
||||
Visit [this](https://docs.dapr.io/developing-applications/building-blocks/pubsub/) link for more information about Dapr and Pub-Sub.
|
||||
|
||||
> **Note:** if you are looking for the example using the Dapr SDK client (recommended) [click here](../csharp/).
|
||||
> **Note:** This example leverages the Dapr client SDK. If you are looking for the example using only HTTP [click here](../csharp-http/).
|
||||
|
||||
This quickstart includes one publisher:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,9 +1,11 @@
|
|||
# Dapr pub/sub
|
||||
# Dapr pub/sub (HTTP requests client)
|
||||
|
||||
In this quickstart, you'll create a publisher microservice and a subscriber microservice to demonstrate how Dapr enables a publish-subcribe pattern. The publisher will generate messages of a specific topic, while subscribers will listen for messages of specific topics. See [Why Pub-Sub](#why-pub-sub) to understand when this pattern might be a good choice for your software architecture.
|
||||
|
||||
Visit [this](https://docs.dapr.io/developing-applications/building-blocks/pubsub/) link for more information about Dapr and Pub-Sub.
|
||||
|
||||
> **Note:** This example leverages HTTP `requests` only. If you are looking for the example using the Dapr Client SDK (recommended) [click here](../python/).
|
||||
|
||||
This quickstart includes one publisher:
|
||||
|
||||
- Python client message generator `checkout`
|
||||
|
|
|
|||
|
|
@ -4,6 +4,8 @@ In this quickstart, you'll create a publisher microservice and a subscriber micr
|
|||
|
||||
Visit [this](https://docs.dapr.io/developing-applications/building-blocks/pubsub/) link for more information about Dapr and Pub-Sub.
|
||||
|
||||
> **Note:** This example leverages the Dapr client SDK. If you are looking for the example using only HTTP `requests` [click here](../python-http/).
|
||||
|
||||
This quickstart includes one publisher:
|
||||
|
||||
- Python client message generator `checkout`
|
||||
|
|
|
|||
Loading…
Reference in New Issue