“It’s 2019 so apparently everyone has a service mesh. Istio has been the most hyped – it has solid corporate backing from IBM, Google, Pivotal and SAP. These companies now need to do a better job of nailing use cases.”
HashiConf EU 2019: The Service Mesh push and Progressive Delivery
“The latter piece can be the tricky one when using containers to develop microservices. How do you link up all the component parts when they may be spread across a cluster of server nodes, and instances of them are continually popping up and later being retired as they are replaced by updated versions? In a service-oriented architecture (SOA), which microservices can be seen as the evolutionary heir to, this kind of task is analogous to that taken care of by an enterprise service bus (ESB). So what is needed is a kind of cloud-native version of an ESB…. This is the job that Istio, a relatively new open source project, aims to fill. It is officially described as a service mesh, because parts of it are distributed across the infrastructure alongside the containers it manages, and it sets out to meet the requirements of service discovery, load balancing, message routing, telemetry, and monitoring – and, of course, security.”
Original source: Istio Aims To Be The Mesh Plumbing For Containerized Microservices
Round-up of developer related stuff from Google.
Original source: Google Cloud Platform Blog: Cloud Services Platform: bringing the best of the cloud to you
“The software serves as a management mechanism for distributed microservices, providing capabilities like traffic management, service identity and security, policy enforcement and telemetry among apps running across multiple Kubernetes clusters and hosts.”
Original source: Istio sets sail as Red Hat renovates OpenShift container ship