I wondered the same thing. I assume because it was talking about Envoy, which Lyft uses, and perhaps there was a problem mentioning their name and association with Envoy in this video. Or the editor screwed up :) We had a private Demo from the AWS folks which described this missing info to us recently. So I think it is a somewhat educated guess.
Yeah. I don't mind missing the info on Envoy, but the video picks up in the middle of "application observability', which was what I was trying to figure out.
At 38:45 - Why does traffic from the ALB not pass through the envoy proxy? Also at this point he says "there are actually three (envoys) running" - where is the third?
Looks like this thing doesn't work with Lambda.. in which case it is a no go. Most micro services have api gateway in front, connecting to lambdas, which may connect to more lambdas. So this thing is unusable.
demo starts at 20:30
Thank you
Cheers :D
An open source alternative is: Istio Service Mesh
What happened at 30:57 ?
I wondered the same thing. I assume because it was talking about Envoy, which Lyft uses, and perhaps there was a problem mentioning their name and association with Envoy in this video. Or the editor screwed up :) We had a private Demo from the AWS folks which described this missing info to us recently. So I think it is a somewhat educated guess.
Censorship ... or just recoding issues: it happens also after this (eg, 33:52). Of course, just when he was clarifying or introducing a subject ... ;)
Yeah. I don't mind missing the info on Envoy, but the video picks up in the middle of "application observability', which was what I was trying to figure out.
At 38:45 - Why does traffic from the ALB not pass through the envoy proxy? Also at this point he says "there are actually three (envoys) running" - where is the third?
Ah, at 39:20 he says the diagram is off, traffic goes from ALB into Gateway's envoy first.
Lovely presentation!
Thank you! That's AWSome to hear! 😀 🙌
brilliant!! Thank you
Video has been edited multiple interesting topics have been cut, disappointed
Looks like this thing doesn't work with Lambda.. in which case it is a no go. Most micro services have api gateway in front, connecting to lambdas, which may connect to more lambdas. So this thing is unusable.