Signed-off-by: Paul Yuknewicz <paulyuk@microsoft.com> |
||
---|---|---|
.. | ||
order-processor | ||
README.md | ||
dapr.yaml | ||
makefile |
README.md
Dapr state management (HTTP Client)
In this quickstart, you'll create a microservice to demonstrate Dapr's state management API. The service generates messages to store in a state store. See Why state management to understand when to use this API.
Visit this link for more information about Dapr and State Management.
Note: This example leverages HTTP
requests
only. If you are looking for the example using the Dapr Client SDK (recommended) click here.
This quickstart includes one service:
- Dotnet client service
order-processor
Run all apps with multi-app run template file
This section shows how to run applications at once using multi-app run template files with dapr run -f .
. This enables to you test the interactions between multiple applications.
- Open a new terminal window and run
order-processor
using the multi app run template defined in dapr.yaml:
cd ./order-processor
dotnet restore
dotnet build
cd ..
- Run the Dotnet service app with Dapr:
dapr run -f .
dapr stop -f .
Run a single app at a time with Dapr (Optional)
An alternative to running all or multiple applications at once is to run single apps one-at-a-time using multiple dapr run .. -- dotnet run
commands. This next section covers how to do this.
- Run the Dotnet service app with Dapr:
cd ./order-processor
dapr run --app-id order-processor --resources-path ../../../resources/ -- dotnet run
- Stop and clean up application processes
dapr stop --app-id order-processor