In future we will have some sort of light weight mediation also embedded in API microgateway. In such cases we will have mediation extensions in addition to API definition. So completely depend on API definition will be problematic as we cannot embed such logic there. Thoughts?
Thanks, sanjeewa. On Mon, Jul 29, 2019 at 10:00 AM Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Manjula, > > We have already scheduled a meeting to discuss the project. Will add you > to the meeting. > > Thank you! > > On Mon, Jul 29, 2019 at 9:52 AM Manjula Rathnayake <manju...@wso2.com> > wrote: > >> Hi Pubudu, >> >> Shall we schedule a meeting and discuss the use cases and proceed? >> >> Thank you. >> >> On Fri, Jul 26, 2019 at 2:36 PM Pubudu Gunatilaka <pubu...@wso2.com> >> wrote: >> >>> Hi Nuwan, >>> >>> On Thu, Jul 25, 2019 at 5:19 PM Nuwan Dias <nuw...@wso2.com> wrote: >>> >>>> Looks like our cloud team has done this already for the synapse based >>>> gateway. Maybe we could learn some things from them. >>>> >>> >>> Will check with the Cloud team as well. >>> >>>> >>>> Do we want to build a UI experience for this? Like the deployment >>>> happens when you press a button on the UI or is it preferable to build a >>>> mode where you save some stuff somewhere when you press the button and then >>>> get a CLI to do the actual deployment? I'm Asking because of the CI/CD >>>> aspects and to make the runtime somewhat disconnected from the design time. >>>> >>> >>> The plan is to build a UI as well. Followings are the expectations. >>> >>> 1. When a user publishes the API, he clicks on a button which says >>> "Publish in a private Jet Mode". Then this API gets deployed in K8s. >>> 2. In a separate UI, he has the option to combine multiple APIs and then >>> deploy those APIs in single microgateway. >>> 3. The microgateway manage UI contains information such as microgateway >>> service endpoint, the number of replicas, the health status of the >>> gateways, scale gateways manually, etc. >>> >>> For CI/CD, we can use the apimCLI and do the deployment. The APIs >>> created in the publisher can be exported with the relevant artifacts >>> required for K8s deployment. Then that can be used to deploy in K8s. >>> >>> Thank you! >>> -- >>> *Pubudu Gunatilaka* | Associate Technical Lead | WSO2 Inc. >>> (m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com >>> <http://wso2.com/signature> >>> >>> >> >> -- >> *Manjula Rathnayaka* | Senior Technical Lead | WSO2 Inc. >> (m) +94 77 743 1987 | (w) +94 11 214 5345 | (e) manju...@wso2.com >> GET INTEGRATION AGILE >> Integration Agility for Digitally Driven Business >> > > > -- > *Pubudu Gunatilaka* | Associate Technical Lead | WSO2 Inc. > (m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com > <http://wso2.com/signature> > > -- *Sanjeewa Malalgoda* Software Architect | Associate Director, Engineering - WSO2 Inc. (m) +94 712933253 | (e) sanje...@wso2.com | (b) Blogger <http://sanjeewamalalgoda.blogspot.com>, Medium <https://medium.com/@sanjeewa190> GET INTEGRATION AGILE <https://wso2.com/signature> Integration Agility for Digitally Driven Business
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
