MuleSoft Misses the Mark With Anypoint Service Mesh

published 04.06.2020 02:00

Share

One of the key points of breaking up a monolithic application into microservices is so that teams can more rapidly make changes by being loosely coupled from other services.

A microservice that knows both a warehouse’s definition of a book and a retail store’s definition of a book is instead loosely scoped and tightly coupled between two contexts.

This allows all the features of Mule’s API management to be applied to your Istio microservices, including: Discoverability through Mule Exchange to maximize the reuse of your microservices across your enterprise and make it easy for other teams to request access to your microservice.

Anypoint Service Mesh The key take-away I got from the description of Anypoint Service Mesh is that you point it at your an instance of Istio, either your own or one managed by Mule, and then you can manage the Istio microservices in Mule.

What MuleSoft seems to be missing with this half baked Anypoint so-called “Service Mesh” is that microservices are not integration.