For those unaware, istio is a service mesh. In short, it "manages" your micro-services. Eg. How they connect together and much much more.<p>Look at what it does and you will see the overhead of what people don't mention in the first talk :p<p>In a way, I think Istio is the opposite of a microservice ( didn't look at the code, but I see 840 issues in the github repository)
One of the more important changes:<p>> Policy Checks Off By Default. Changed policy checks to be turned off by default to improve performance for most customer scenarios.<p>Given that the Mixer policy engine is a big selling point of Istio, it is disappointing that it hurts performance so much they decided to disable it by default.