This article serves as a summary for the session Istio Simplified at ServiceMeshCon, KubeCon Europe 2020. Session was presented by Louis Ryan from Google and Steve Dake from IBM.
Google has been working on making Istio simpler to install, upgrade, administer and use.
Istio was built using microservices principles where it was divided into various components based on the functionality they provided. The diagram below shows various components of 1.4 version.
This component division was made with the assumption that separate teams would deploy and administer each of the components. However, in reality, there is usually one team/person maintaining and administering Istio and they don’t make use of the flexibility provided by individual components. They just want to deploy, maintain and upgrade Istio. This is one of the example scenarios where microservices architecture may not be beneficial based on client usage.
So, in order to remove this over pivoted design that tries to accommodate one potential solution and make it simple for the primary user a shift to monolith architecture has been made:
Our original Kubernetes tool list was so popular that we've curated another great list of tools to help you improve your functionality with the platform.
Microsoft’s Open Service Mesh is an SMI-compliant, lightweight service mesh being run as an open source project. Backed by service-mesh…
Just as tech is revised and upgraded, so too should a tool comparison be. Service meshes act as the substrate to connect microservices, find the one for you.
For teams to monitor, support, and to maintain these services is becoming a challenge so most enterprises have invested in some kind of microservices management tool.
As part of my learning in devops space, I started exploring service mesh and recently did a podcast. Here is the blog version which I think will be useful for others to get the big picture. This post assumes you are aware of how kubernetes works at a high level