rshriram
Re:Google and IBM announce Istio – easily secure and manage microservices
on Wednesday May 24, 2017 @12:03PM (#14411015)
The overlap with Linkerd is around routing, resilience, metrics/tracing, and the deployment model (at high level).
Our deployment model is a bit more transparent. Traffic gets transparently routed via Envoy, without using HTTP_PROXY or direct addressing of sidecars. This implies zero change to application code.
Secondly, Istio brings two more things to the table: policy enforcement (rate limits, ACLs, etc.), and authentication/authorization. Istio enables mutual TLS auth between services with automatic certificate management. The policy plane is extensible, where you can plug in adapters or specific policy implementations.
Re:Google and IBM announce Istio – easily secure and manage microservices
on Wednesday May 24, 2017 @11:57AM (#14410962)
IBM's announcement: https://developer.ibm.com/dwblog/2017/istio/
Re:Google and IBM announce Istio – easily secure and manage microservices
on Wednesday May 24, 2017 @11:55AM (#14410946)
It depends on how you view it. Baking everything into the application logic works if you have a homogeneous stack. When you start going down the polyglot route, with 5-6 language runtimes, multiple databases, it becomes really really hard to maintain all the communication logic (discovery, load balancing, resilience) in the app code.
Take a look at AirBnB's smartstack, Yelp, Lyft's Envoy mesh. These are all polyglot applications, where the communication aspects are abstracted out into sidecars.