Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS App Mesh – Service Mesh for Microservices on AWS

aws.amazon.com

Post reply on HN
Print view View original

1–10 of 36 posts

Re: AWS App Mesh – Service Mesh for Microservices on AWS

#6

Post by jsmeaton »

gauravphoenix wrote: post #2

like Istio?

Perhaps you can help me out. I'm wondering where Istio (and other meshes) fit into the picture when deploying to k8s. The Itsio docs mention it is deployed as a side car, but is that within each pod? And are Service objects still required?

Here is my mental model of a traditional deployment (EKS):

Service[Type: LoadBalancer] -> Deployment[Pod]

How does Itsio fit into this scenario, or what does it replace?

Re: AWS App Mesh – Service Mesh for Microservices on AWS

#8

Post by manigandham »

jsmeaton wrote: post #6
gauravphoenix wrote: post #2

like Istio?

Perhaps you can help me out. I'm wondering where Istio (and other meshes) fit into the picture when deploying to k8s. The Itsio docs mention it is deployed as a side car, but is that within each pod? And are Service objects still required? Here is my mental model of a traditional deployment (EKS): Service[Type: LoadBalancer] -> Deployment[Pod] How does Itsio fit into this scenario, or what does it replace?

Generally traffic is defined as north/south (into and out of the datacenter) or east/west (between servers in the datacenter).

Istio is for east/west traffic within your K8S cluster, designed to connect your services together by moving all the network traffic through the Envoy proxy. It is usually done by wrapping your deployments with an extra sidecar pod (automatically using K8S APIs) that intercepts all the networking to other services and pods. You would still use a load balancer or ingress to route external traffic into the cluster, although there are options like Heptio Contour that also use Envoy for this.

This provides a single data and control plane to centralize all network reliability, security, service discovery, and monitoring.

Re: AWS App Mesh – Service Mesh for Microservices on AWS

#9

Post by jeremyjh »

manigandham wrote: post #8
jsmeaton wrote: post #6

Earlier quoted context omitted.

Perhaps you can help me out. I'm wondering where Istio (and other meshes) fit into the picture when deploying to k8s. The Itsio docs mention it is deployed as a side car, but is that within each pod? And are Service objects still required? Here is my mental model of a traditional deployment (EKS): Service[Type: LoadBalancer] -> Deployment[Pod] How does Itsio fit into this scenario, or what does it replace?

Generally traffic is defined as north/south (into and out of the datacenter) or east/west (between servers in the datacenter). Istio is for east/west traffic within your K8S cluster, designed to connect your services together by moving all the network traffic through the Envoy proxy. It is usually done by wrapping your deployments with an extra sidecar pod (automatically using K8S APIs) that intercepts all the networ…

GP asked about Service objects though. k8s natively provides name resolution, traffic routing and load balancing to your defined service objects. So what does Envoy do for me that k8s does not do itself?
Post reply on HN