From ec8bcb59812c129fd440d4303df1fbb40ebc1478 Mon Sep 17 00:00:00 2001 From: Aaron Schlesinger Date: Tue, 5 May 2020 13:18:16 -0700 Subject: [PATCH] Moving service invocation use case out And into the concepts doc --- concepts/service-invocation/README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/concepts/service-invocation/README.md b/concepts/service-invocation/README.md index 2a98409fe..4f81aefa6 100644 --- a/concepts/service-invocation/README.md +++ b/concepts/service-invocation/README.md @@ -2,6 +2,10 @@ Dapr-enabled apps can communicate with each other through well-known endpoints in the form of http or gRPC messages. +Using the service invocation API, your microservice can find and reliably communicate with other microservices in your system. + +Below is a high level overview of how Dapr's service invocation system works. + ![Service Invocation Diagram](../../images/service-invocation.png) 1. Service A makes a http/gRPC call meant for Service B. The call goes to the local Dapr sidecar. @@ -23,7 +27,8 @@ The following describes items 1-6 again in the context of this sample: Steps 4-5 are the same as the list above. -For more information, see: +# Next Steps -- The [Service Invocation API Spec](../../reference/api/service_invocation_api.md) -- A [HowTo](../../howto/invoke-and-discover-services/README.md) on Service Invocation +**If you're ready to get started**, follow this how-to guide on [how to get started with service invocation](https://github.com/dapr/docs/tree/master/howto/invoke-and-discover-services) + +If you'd like more technical detail on how service invocation works, move on to the [API Spec](../../reference/api/service_invocation_api.md)