Hi Shabir, +1 for the suggestion. I also believe that “Terminating an API call sooner helps on releasing the resources on the runtime gateway”. As per the image on [1] for an “application-level” throttled out API call; it still passes through “API-Level” throttling.
BTW the “order” each filter appear doesn’t make any performance improvement on “successive” API calls (unless it can be implemented or processed parallel). Suppose your API call deserves a valid grant. Still it has to pass through all API-Level -> Application-Level -> Resource-Level filters. [1] https://docs.wso2.com/display/AM190/Key+Concepts#KeyConcepts-API-levelthrottling Thank you On Thu, Aug 6, 2015 at 12:41 PM, Shabir Mohamed <[email protected]> wrote: > Hi, > > According to our APIM docs[1], throttling is handled in the following > order: > > *API-Level* > *Application-Level * > *Resource-Level*. > > As per my understanding the purpose of an Application is to group a set of > similar user-subscribed APIs. > > Then shouldn't we be checking for the Application-Level first and then > check whether the API can be granted access to? Because we could have > multiple APIs in an application which haven't reached their throttling > level whilst the application itself could have passed the limit? > > Please correct me if I'm missing anything here.... > > [1] https://docs.wso2.com/display/AM190/Key+Concepts > ------------------------------------- > *Shabir Mohamed* > *Software Engineer* > WSO2 Inc.; http://wso2.com > Email: [email protected] <[email protected]> > Mobile: +94 77 3516019 | +94 71 6583393 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- With Regards, *Rasika Perera* Software Engineer M: +94 71 680 9060 E: [email protected] LinkedIn: http://lk.linkedin.com/in/rasika90 WSO2 Inc. www.wso2.com lean.enterprise.middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
