With the emergence of microservice architecture (MSA), software architects and developers are increasingly adopting microservices for faster innovation. Smaller teams, agile software development life cycles, freedom to use heterogeneous technologies, and early feedback cycles are the key drivers for its success. But MSA comes with its own challenges. Because of this disaggregation of architectures, the number of endpoints is exploding. Communication among these endpoints will be a key challenge. To address this, software architects came up with a very promising, future proof software architecture known as a Service Mesh.
Multiple implementations of Service Meshes exist, however none of them have been able to address the concern on how APIs can be exposed in a controlled and secure manner to its API consumers. WSO2 API Manager provides out of the box integration with Isitio Service Mesh, which allows one or more APIs from Isitio mesh to be exposed for consumption via the API Manager.
In this session, we will explain how services meshes and API management can co-exist. We will also draw references to WSO2 API Manager and how it can be used with Isitio to manage APIs that are exposed for consumption.