# 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 data in a state store. See [Why state management](#why-state-management) to understand when this pattern might be a good choice for your software architecture. Visit [this](https://docs.dapr.io/developing-applications/building-blocks/state-management/) 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](../sdk/). This quickstart includes one service: Node client service `order-processor` This section shows how to run applications at once using [multi-app run template files](https://docs.dapr.io/developing-applications/local-development/multi-app-dapr-run/multi-app-overview/) 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](./dapr.yaml): 1. Open a new terminal window and navigate to `order-processor` directory: ```bash cd ./order-processor npm install cd .. ``` 2. Run the Node service app with Dapr: ```bash dapr run -f . ``` 3. Stop and cleanup application process ```bash 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 .. -- npm start` commands. This next section covers how to do this. ## Run Node service with Dapr 1. Navigate to folder and install dependencies: ```bash cd ./order-processor npm install ``` 2. Run the Node service app with Dapr: ```bash dapr run --app-id order-processor --resources-path ../../../resources/ -- npm start ``` 2. Stop and cleanup the process ```bash dapr stop --app-id order-processor ```