quickstarts/pub_sub/javascript/sdk
Amulya Varote ac52d39dfd Changed port numbers and app ids
Signed-off-by: Amulya Varote <amulyavarote@microsoft.com>
2022-08-30 16:03:55 -07:00
..
checkout Update JS-SDK package from dapr-client to @dapr/dapr (#710) 2022-07-20 16:43:22 -07:00
order-processor Changed port numbers and app ids 2022-08-30 16:03:55 -07:00
README.md Changed port numbers and app ids 2022-08-30 16:03:55 -07:00
makefile Removed docker image prefix addition step 2022-07-25 12:28:57 -07:00

README.md

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 to understand when this pattern might be a good choice for your software architecture.

Visit this 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.

This quickstart includes one publisher:

  • Node client message generator checkout

And one subscriber:

  • Node subscriber order-processor

Run Node message subscriber with Dapr

  1. Install dependencies:
cd ./order-processor
npm install
  1. Run the Node publisher app with Dapr:
dapr run --app-port 5002 --app-id order-processing-sdk --app-protocol http --dapr-http-port 3501 --components-path ../../../components -- npm run start

Run Node message publisher with Dapr

  1. Install dependencies:
cd ./checkout
npm install
  1. Run the Node publisher app with Dapr:
dapr run --app-id checkout-sdk --app-protocol http --dapr-http-port 3500 --components-path ../../../components -- npm run start
dapr stop --app-id checkout-sdk
dapr stop --app-id order-processor-sdk