Managing a service mesh is like baking a pie. You need to have many ingredients in place to complete the pie before it can be served.
Let’s start with the definition for a service mesh. A service mesh is used to define the system of microservices that incorporates interactions between applications. As a service mesh gains traction and expands in size, it becomes more complicated to manage.
Manage a service mesh
In order to gain control when you manage a service mesh, you need to understand that it requires elements such as detection, stability, recovery, as well as monitoring properties. With some additional ingredients such as rate limits, circuit breaking, A/B testing, roll outs and validation, you can have full-on control over the outcome.
Let’s start with AMPLIFY Integration Builder (iPaaS); you will also be using the AMPLIFY Catalog to share your work with your consumers. Then, to expose the mesh APIs/Service to consumers, you will use AMPLIFY Central. Further, to expose and secure Mesh APIs, it’s necessary to have AMPLIFY API Builder.
Finally, you need to build new services to extend existing AMPLIFY Mesh Governance (Hybrid). This ties together a nice pie which provides mesh flow policies to services where API access can be monitored, as well as governed.
A service mesh makes your APIs and services more secure. But take note, a service mesh is not a replacement for API Management -nor should it be.
When you use AMPLIFY Central to administer your microservices, you can control and manage API traffic and mesh services for many locations, and across many service mesh environments. First and foremost, service meshes are able to provide this type of traffic control for your on-premises (Kubernetes) clusters. Thanks to their main function which is to manage service-to-service interaction, they can provide these features rather easily.
However, due to the fact that they are designed to effectively connect a source call to its optimal destination service instance, many of these traffic control features are destination-oriented.
AMPLIFY Central can be used to give you that “overview” of configuration, status and activity across these many distributed mesh (and other managed gateway) environments.
READ MORE: The role of APIs in microservices.
In other words, service meshes are certainly tailored to balance and manage individual calls across a number of destinations. Yet they are rather unsuitable to control traffic from a number of origins to a specific place or to control traffic across an entire service landscape. AMPLIFY Central can provide you a consolidated view of traffic across various cloud and on-premises environments.
Be in the know! Discover more about Mesh governance.