mirror of https://github.com/hashicorp/consul
Backport of Update service-discovery.mdx into release/1.14.x (#15862)
* backport of commitpull/15875/head93fc1a3b96
* backport of commite6921def76
Co-authored-by: Vladislav Sharapov <vladislav.sharapov@proton.me> Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
parent
ddd12e6c1b
commit
e0c47559da
|
@ -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:
|
||||
|
||||
|
|
Loading…
Reference in New Issue