mirror of https://github.com/dapr/docs.git
Changed image name in the docs
This commit is contained in:
parent
40cfca74a7
commit
5bc88ab6d0
|
|
@ -12,7 +12,7 @@ This article describe how to deploy services each with an unique application ID,
|
|||
|
||||
The below code examples loosely describes an application that processes orders. In the examples, there are two services - an order processing service and a checkout service. Both services have Dapr sidecars and the order processing service uses Dapr to invoke the checkout method in the checkout service.
|
||||
|
||||
<img src="/images/service_invocation_eg.png" width=1000 height=500 alt="Diagram showing service invocation of example service">
|
||||
<img src="/images/building-block-service-invocation-example.png" width=1000 height=500 alt="Diagram showing service invocation of example service">
|
||||
|
||||
## Step 1: Choose an ID for your service
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ In this guide we'll start of with the basics: Using the key/value state API to a
|
|||
|
||||
The below code examples loosely describe an application that processes orders. In the examples, there is an order processing service which has a Dapr sidecar. The order processing service uses Dapr to store state in a Redis state store.
|
||||
|
||||
<img src="/images/state_management_eg.png" width=1000 alt="Diagram showing state management of example service">
|
||||
<img src="/images/building-block-state-management-example.png" width=1000 alt="Diagram showing state management of example service">
|
||||
|
||||
## Step 1: Setup a state store
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 181 KiB After Width: | Height: | Size: 181 KiB |
Loading…
Reference in New Issue