How API Connect will coexist with Service Mesh-Istio
Microservices architecture proved to be the way to go for organizations to reduce the time to market, take advantage of the cloud, and reduce costs by using a container technology such as docker and Kubernetes. However, organizations have been struggling to implement service discovery, load balancing, failure recovery, metrics, and monitoring. As well as A/B testing, canary releases, rate limiting, access control, and end-to-end authentication in every new project. Service Mesh-Istio was created as an open source project to externalize all of these functionalities to an external component so it becomes part of the platform instead of adding these functionalities to each microservice-based project.
API Connect is an API management solution that was developed to provide a platform to secure, manage and monitor APIs. Each microservice in our solution might consume one or many APIs. API Connect is still needed to connect to the backend systems through APIs from microservices and expose any of the microservices as APIs to external developers.
In this presentation, we will explain Service Mesh-Istio open source project and its implementation in IBM Cloud Private. In order to tie that to microservices, we will set the stage by exploring the microservice architecture. Then we will discuss the importance of having IBM API Connect in the organization to coexist with Service Mesh-Istio. Cedrus will detail how the to-be solution architecture will look like having API Connect and Service Mesh-Istio.