Adding Service Mesh reference
Adding Service Mesh reference for Consul
This commit is contained in:
parent
ce7ab8abc1
commit
62a84697a1
|
@ -24,8 +24,10 @@ Consul provides several key features:
|
||||||
* **Multi-Datacenter** - Consul is built to be datacenter aware, and can
|
* **Multi-Datacenter** - Consul is built to be datacenter aware, and can
|
||||||
support any number of regions without complex configuration.
|
support any number of regions without complex configuration.
|
||||||
|
|
||||||
* **Service Segmentation** - Consul Connect enables secure service-to-service
|
* **Service Segmentation/Service Mesh** - Consul Connect enables secure service-to-service
|
||||||
communication with automatic TLS encryption and identity-based authorization.
|
communication with automatic TLS encryption and identity-based authorization. Applications
|
||||||
|
can use sidecar proxies in a service mesh configuration to automatically establish TLS
|
||||||
|
connections for inbound and outbound connections without being aware of Connect at all.
|
||||||
|
|
||||||
Consul runs on Linux, Mac OS X, FreeBSD, Solaris, and Windows. A commercial
|
Consul runs on Linux, Mac OS X, FreeBSD, Solaris, and Windows. A commercial
|
||||||
version called [Consul Enterprise](https://www.hashicorp.com/products/consul)
|
version called [Consul Enterprise](https://www.hashicorp.com/products/consul)
|
||||||
|
|
Loading…
Reference in New Issue