From 629878a6879c02f47405d066f9277ca945042d6b Mon Sep 17 00:00:00 2001 From: Vladislav Sharapov Date: Tue, 20 Dec 2022 23:54:33 +0400 Subject: [PATCH] Update service-discovery.mdx (#15832) * Update service-discovery.mdx * Update website/content/docs/concepts/service-discovery.mdx Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> --- website/content/docs/concepts/service-discovery.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/concepts/service-discovery.mdx b/website/content/docs/concepts/service-discovery.mdx index b1b4123e21..122e5a05bf 100644 --- a/website/content/docs/concepts/service-discovery.mdx +++ b/website/content/docs/concepts/service-discovery.mdx @@ -21,7 +21,7 @@ Service discovery provides benefits for all organizations, ranging from simplifi - Faster deployment times achieved by high-speed discovery - Automated service registration and de-registration -## How does a service mesh work? +## How does service discovery work? Service discovery uses a service's identity instead of traditional access information (IP address and port). This allows you to dynamically map services and track any changes within a service catalog. Service consumers (users or other services) then use DNS to dynamically retrieve other service's access information from the service catalog. The lifecycle of a service may look like the following: