Difference between revisions of "Service mesh"
Jump to navigation
Jump to search
↑ https://aws.amazon.com/about-aws/whats-new/2019/03/aws-app-mesh-is-now-generally-available/
| (3 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
* [[Traefik]] (2015) | * [[Traefik]] (2015) | ||
* [[Kubernetes networking]] | * [[Kubernetes networking]] | ||
| − | * [[Kiali]] | + | * [[Kiali]] service mesh observability and configuration |
| + | * [[Kong Mesh]] | ||
== See also == | == See also == | ||
* {{Service mesh}} | * {{Service mesh}} | ||
* {{Kubernetes networking}} | * {{Kubernetes networking}} | ||
| − | |||
[[Category:containers]] | [[Category:containers]] | ||
Latest revision as of 19:37, 14 May 2024
wikipedia:Service mesh is a dedicated infrastructure layer for facilitating service-to-service communications between microservices, often using a sidecar proxy.
Related terms[edit]
- Traefik (2015)
- Kubernetes networking
- Kiali service mesh observability and configuration
- Kong Mesh
See also[edit]
- Service mesh: Istio, Linkerd, Consul, containerpilot, AWS App Mesh, Kiali, INNOQ, Kuma, Kong Mesh
- Kubernetes networking: network policies, Network Policy Providers, CNI, Calico, flannel, Service mesh, Istio,
kube-proxy, coredns, AWS VPC CNI: vpc-cni, Kubernetes: Ingress controllers, IPVS, ServiceTypes:LoadBalancer, ClusterIP, NodePort, ExternalName, Endpoints, EndpointSlices, Kubernetes DNS,svc.cluster.local, Weave Net
Advertising:
