On Thu, Mar 14, 2019 at 2:23 PM Rajith Roshan <[email protected]> wrote:
> Hi all, > Currently in microgateway(MGW) when we create the project directory we > fetch all the subscription and application policies and we generate the > source for each policy. In each policy there is ever running loop > (forever), in back ground to update the throttle counters. But the issue > some of the subscription policies(tiers) might not be used in any of the > APIS in MGW and these not used policies running in the background might be > consuming some CPU cycles > > So we thought of filter out the subscription policies(tiers) which are > attached to any of the APIs exposed via MGW. > For ex if API Foo is attach with policy 100PerMin and API Bar is attached > with policies 75PerMin and 50PerMin , then if we are only exposing API > "Foo" and "Bar" from MGW we will only create source files for those > subscription policies only, even though there are many subscription > policies defined in the admin portal of APIM. > Do you find any issues with this approach > We will able to filter some subscription policies with this approach. But it will not be possible for application policies. But in case of API is updated and changed the subscription policies it is required to build the MG again. > > -- > *Rajith Roshan* | Associate Technical Lead | WSO2 Inc. > (m) +94-717-064-214 | (e) [email protected] <[email protected]> > > <https://wso2.com/signature> > -- Rukshan Chathuranga. WSO2, Inc. +94711822074
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
