3 years ago

Category: Software, Database, Kubernetes, Docker, Infrastructure

When compared to the traditional Monolithic way, a Microservice Architecture treats each microservice as a standalone entity/module, essentially helping to ease the maintenance of its code and related infrastructure. Each microservice of an application can be written in a different technology stack, and further be deployed, optimized and managed independently.

This includes basic network functions used by a microservice to initiate a network call and connect with the service mesh sidecar proxy.

As explained in the sections above, in a Microservice Architecture, Istio does this by forming an infrastructure layer to connect, secure and control communication among distributed services.

In this article today, we got an understanding of how a Service Mesh is critical towards the implementation of a Microservice Architecture, and how Istio solves the purpose of achieving those.Taking a step further, in the next article, we would go through the steps involved in installing Istio on different platforms, including Kubernetes.