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

11–20 of 36 posts

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

#11

Post by gauravphoenix »

jeremyjh wrote: post #9
manigandham wrote: post #8

Earlier quoted context omitted.

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?

things like layer 7 control, you can say - "don't allow HTTP GET on /supersecret". Also, Isito is gRPC aware

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

#12

Post by staticassertion »

yodon wrote: post #7

Would this be suitable for an actor-based system (where we want to think of each actor as a routeable microservice)?

Assuming your actors use queues, as they traditionally would, I don't think so. You don't really need service mesh if your communication is a queue, right?

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

#13

Post by willejs »

I am looking forwards to digging in to this a bit more and figuring out how this compares to Istio. I am guessing integration with AWS services such as X-ray and Cloudwatch/logs are the selling point. Still, I am a bit weary about configuring things that run inside your Kubernetes cluster through amazon apis, and not k8s resources. However, you could easily create a custom resource for this. Maybe that is to come? EKS is still young and they are yet to figure a lot of things out, from what i've seen, the roadmap is promising though. I have been working with it a lot, kops still wins for small/medium workloads in production, but I doubt for much longer.

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

#14

Post by manigandham »

jeremyjh wrote: post #9
manigandham wrote: post #8

Earlier quoted context omitted.

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?

More protocol support, retries, rate-limits, circuit-breakers, traffic mirroring, better load-balancing, faster proxy performance, complex routing, fine-grained security policies with pluggable authentication, and in-depth monitoring with integrated tracing.

Smaller clusters or services don't need it. The docs overview page is worth a read: https://istio.io/docs/concepts/what-is-istio/

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

#15

Post by jsmeaton »

manigandham wrote: post #14
jeremyjh wrote: post #9

Earlier quoted context omitted.

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?

More protocol support, retries, rate-limits, circuit-breakers, traffic mirroring, better load-balancing, faster proxy performance, complex routing, fine-grained security policies with pluggable authentication, and in-depth monitoring with integrated tracing. Smaller clusters or services don't need it. The docs overview page is worth a read: https://istio.io/docs/concepts/what-is-istio/

Thanks! I was wondering if mesh effectively replaces services and why, and you've answered that.

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

#16

Post by shubha-aws »

willejs wrote: post #13

I am looking forwards to digging in to this a bit more and figuring out how this compares to Istio. I am guessing integration with AWS services such as X-ray and Cloudwatch/logs are the selling point. Still, I am a bit weary about configuring things that run inside your Kubernetes cluster through amazon apis, and not k8s resources. However, you could easily create a custom resource for this. Maybe that is to come? EK…

shubha from AWS here, we built App Mesh to enable customers to use microservices in any compute service in AWS - be it ECS, Fargate, EKS or even directly on EC2. You configure capabilities using APIs and App Mesh configures Envoy proxies deployed with your pods.

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

#18

Post by sokoloff »

jugg1es wrote: post #17

AWS is totally killing it this week. This is like the 10th major release I've seen since monday.

Well, it’s Re:Invent this week (AWS’ major annual conference), so this is fairly typical. Expect another handful or so of announcements tomorrow during Werner Vogel’s keynote as well.

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

#19

Post by yodon »

staticassertion wrote: post #12
yodon wrote: post #7

Would this be suitable for an actor-based system (where we want to think of each actor as a routeable microservice)?

Assuming your actors use queues, as they traditionally would, I don't think so. You don't really need service mesh if your communication is a queue, right?

I was wondering more about orchestration of the actors... something needs to be responsible for spawning them onto machines and something needs to be responsible for tracking where they are or where their queues are. I love MSFT Orleans but I'd love even more something that fit easier into a conventional node.js and docker kind of world (C# is great but when I look at adoption curves Typescript seems to be growing fast while C# seems to be at best holding steady)

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

#20

Post by burtonator »

willejs wrote: post #13

I am looking forwards to digging in to this a bit more and figuring out how this compares to Istio. I am guessing integration with AWS services such as X-ray and Cloudwatch/logs are the selling point. Still, I am a bit weary about configuring things that run inside your Kubernetes cluster through amazon apis, and not k8s resources. However, you could easily create a custom resource for this. Maybe that is to come? EK…

IS it Istio? Someone on Twitter mentioned it uses the same ports and MIGHT just be Istio...
Post reply on HN