What about the developer first approach? In that case we pre load the default policies to the gateway anyway since there is no indication of an API being associated to a subs throttling policy.
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 > > -- > *Rajith Roshan* | Associate Technical Lead | WSO2 Inc. > (m) +94-717-064-214 | (e) [email protected] <[email protected]> > > <https://wso2.com/signature> > -- *Nuwan Dias* | Director | WSO2 Inc. (m) +94 777 775 729 | (e) [email protected] [image: Signature.jpg]
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
