Member-only story
Service Mesh
We will discuss one of the newest concept of Microservices architecture, which is “Service Mesh”. This is one of the hottest topics in Microservices architecture world and there are growing number of products, implementation and articles. It is also one of the most misunderstood concepts.
In order to take real advantage, we should know what it is and when we should use it or when not to use it.
What is Service Mesh?
In single sentence, it is managing all service-to-service communication aspect in a Microservices architecture. In addition, it provides some additional services that we will explore later.
Problems Solved by Service Mesh
As you know, Microservices communicates between them a lot. We talked a lot about this communication and even discussed some communication patterns such as API gateway and Service discovery. If we do not design communication aspects properly whole system can have issues regardless of how well we designed services.
When we depend so much on inter-service communication, we have to be aware of the challenges it poses. The most notable ones are,
- Timeouts — When the response from the service we call, does not return on time.
- Security — Make sure the data passed between services is as secure as possible and that when possible, there will be secure authentication between the services.
- Retries — We want to do when communication…
