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.
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
wrote:
> Hi Pubudu,
>
> Shall we schedule a meeting and discuss the use cases and proceed?
>
> Thank you.
>
> On Fri, Jul 26, 2019
Hi Nuwan,
On Thu, Jul 25, 2019 at 5:19 PM Nuwan Dias 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
Hi,
We have another option here which is the extended version of option 2.
Option 3:
We are currently developing these custom resources for APIM in Kubernetes.
So in these, what we expect from an external user is the Swagger
definition. So with this Swagger definition, we deploy a micorgateway
