![]() ![]() ![]() Henrik recalled that it's normally difficult to obtain a full view of what rules we've applied in the cluster, and when he first saw Meshery, his immediate thought was, "Wow, this is exactly what is missing in the market at the moment." ![]() In your service to service communication, there are a plethora of scenarios that the service mesh can handle. You can also have traffic splitting if you do canary releases. Therefore a service mesh offers a variety of features like this to manage the certificates within the cluster and and circle them in a regular pace. So if a service A needs to introduce another service B, then the service mesh will manage the retry logic such that if we reach at one time and the service B is not responding then the service mesh will try to reach out several times. When you design microservice architecture, there is a need of implementing retry logic. Henrik goes on to elaborate that in service mesh we can do a lot of things to make sure that the communication is reliable. This structure makes it simple to boost your resiliency. Maybe there's a load balancer in between. If you were to take a three-tiered web or three-tiered app and you think about how you're breaking out those tiers with some amount of kind of vertical scaling, you'd probably, end up putting at least a virtual IP address out in front of the whole web tier and then you've got an app tier and a database tier because you've got multiple instances of those things. The way I prefer to think about a surface mesh is that it's all about resiliency. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |