Interesting, but there's currently a lot of overlap between competing things that want to inject themselves between service consumers and service producers.<p>There's API gateway products (Apigee, Kong, etc). Load balancers and proxies of various types. Caching and CDN products. More niche stuff like bot blocking, and this attempt to bundle control and statistics.<p>It would be nice if some sort of standard pattern emerged, where something was the main orchestrator. At the moment, you can end up with suboptimal stuff. Like a CDN that routes to a cloud API gateway that then routes to a (not geographically close) load balancer, that then hits the actual service.<p>I'm surprised that Cloudflare, Akamai, and the like haven't offered all of these things at the edge. Some things are service to service, but a fair amount is client to service...putting this stuff closer would help.
There seems to be also other companies involved:<p>Redhat: <a href="https://blog.openshift.com/red-hat-istio-launch/" rel="nofollow">https://blog.openshift.com/red-hat-istio-launch/</a><p>Pivotal: <a href="https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise" rel="nofollow">https://content.pivotal.io/blog/pivotal-and-istio-advancing-...</a>
This may be the most important project in distributed computing in a long time. It solves some fundamental problems that layer 3 networking has been unable to tackle. Its initial integration with Kubernetes is great but long term it could be the basis of all application level communication whether it is deployed in a container orchestration system, VMs, bare metal or as an enabler for Lambda (function) frameworks.
What happened to dumb pipes, smart endpoints? We do the same things again that we did before with SOA, having hard-to-replace middleware / bus systems.
Google Cloud Platform Blog Post: <a href="https://cloudplatform.googleblog.com/2017/05/istio-modern-approach-to-developing-and.html" rel="nofollow">https://cloudplatform.googleblog.com/2017/05/istio-modern-ap...</a>
Great documentation and some really great tools included. I was able to get the platform running in minikube really quickly. Interested to compare this to linkerd.
Can someone ELI5 how is this relating to, and complementing, Kubernetes? What does it do that Kube doesn't, and what does Kube do that Istio doesnt?
Regarding API management in the context of Istio:<p><a href="https://apigee.com/about/blog/digital-business/simplifying-microservices-management" rel="nofollow">https://apigee.com/about/blog/digital-business/simplifying-m...</a>
Is the sidecar-container-within-a-pod the only deployment option on Kubernetes currently? Is a daemonset deployment (like what Linkerd does) option currently in the works?
<a href="https://istio.io/docs/concepts/network-and-auth/auth.html" rel="nofollow">https://istio.io/docs/concepts/network-and-auth/auth.html</a><p>No option for OAuth2 or JWT? Maybe I'm not understanding the problem Istio solves vs. Envoy
> Lyft developed the Envoy proxy to aid their microservices journey, which brought them from a monolithic app to a production system spanning 10,000+ VMs handling 100+ microservices.<p>Are those numbers right? Wouldn't it be the other way around realistically?
There is a lot to like about this move. Microservices and service mesh's are certainly an interesting area right now...and this represents a big push from some big players.
In case anyone is interesting in using Azure Container Service with the builtin Kubernetes orchestrator, I wrote an easy tutorial [1] for deploying Istio.<p>[1]: <a href="https://readon.ly/post/2017-05-25-deploy-istio-to-azure-container-service/" rel="nofollow">https://readon.ly/post/2017-05-25-deploy-istio-to-azure-cont...</a>
> Really interested to hear user feedback from today's #istio announcement and where it will have the biggest impact.<p>Okay: I immediately deeply, profoundly, bitterly hate and despise your announcement and for just one, really simple, dirt simple, but totally unforgivable reason: What the heck is a "microservice"? You never said.<p>That word, <i>microservice</i>, is not in a standard English dictionary, so you are writing undefined jargon, gibberish, junk and not English. You are insulting me and even worse yourself.<p>Instead, write English. Get rid of the undefined jargon.<p>Got it?<p>This was a difficult lesson?<p>> the biggest impact<p>Until you learn to communicate at, say, the late elementary grade school level, e.g., learn to write English, the impact promises to be minimal.