From 4e52974a1dc27c15cd9173378189d5ea77256cb3 Mon Sep 17 00:00:00 2001 From: Michael Klich Date: Thu, 3 Oct 2024 14:31:07 +0200 Subject: [PATCH] Update howto-invoke-non-dapr-endpoints.md (#4369) Update service invocation steps according to diagram Signed-off-by: Michael Klich --- .../service-invocation/howto-invoke-non-dapr-endpoints.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints.md b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints.md index 28c3cb8f1ec..680b0361152 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints.md +++ b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-non-dapr-endpoints.md @@ -38,11 +38,9 @@ The diagram below is an overview of how Dapr's service invocation works when inv Diagram showing the steps of service invocation to non-Dapr endpoints 1. Service A makes an HTTP call targeting Service B, a non-Dapr endpoint. The call goes to the local Dapr sidecar. -2. Dapr discovers Service B's location using the `HTTPEndpoint` or FQDN URL. -3. Dapr forwards the message to Service B. -4. Service B runs its business logic code. -5. Service B sends a response to Service A's Dapr sidecar. -6. Service A receives the response. +2. Dapr discovers Service B's location using the `HTTPEndpoint` or FQDN URL then forwards the message to Service B. +3. Service B sends a response to Service A's Dapr sidecar. +4. Service A receives the response. ## Using an HTTPEndpoint resource or FQDN URL for non-Dapr endpoints There are two ways to invoke a non-Dapr endpoint when communicating either to Dapr applications or non-Dapr applications. A Dapr application can invoke a non-Dapr endpoint by providing one of the following: