Hi all, With the usage of ballerina in API Manager 3.0.0, we can do most of the integration part of the API within API Manager.
With that capability, APIs with high integration complexity can be Published and deployed to the Gateway. Other than that, with the new composite APIs [1] feature to be introduced with with APIM 3.0.0, API Manager allows us to create customized APIs by reshaping a collection of APIs as well. With that, an added complexity will be there in such APIs including a combination of multiple services . Since that sort of APIs gives a considerable load to the Gateway and make it complex in operation, we are planning to give the capability to each of those API to be deployed into separate Gateways with *Per API per Gateway Feature*. Following is a sample illustration of the flow with K8. 1. Before publishing the feature the publisher user is facilitated to enable the per API per Gateway feature. 2. If the feature is enabled in API Publisher, the API will be published with an auto generated Label. 3. Using this label, a new gateway will be start up in a container in the Container Management System. 4. The API will be deployed in that newly created Gateway and provide the Access URL and credential related information to the API Manager side. We are going to support *K8* and *Openshift* by default in this feature. And next, we will provide extension point to support other Container Management Systems as well. [1] mail thread : [C5] API composition support for application developers in API Store Thanks & Regards, *Chamalee De Silva* Software Engineer *WS**O2* Inc. :http://wso2.com/ Office :- *+94 11 2145345 <%2B94%2011%202145345>* mobile :- *+94 7 <%2B94%2077%202782039>1 4315942*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
