Hi,

Current Throttling capabilities of API Manager only allows defining user
wise and Application wise Access Quotas.


For example when considering an Application and a set of APIs Subscribed,
like below (tier limit is shown next to the API)

Application-1 (1000 Req/min)
|
+-+API-1 (10 Req/min)
|
+-+API-2 (1 Req/min)
|
+-+API-3 (5 Req/min)

each new token would allow end-users to make the number of requests defined
by the tier. Using a token generated for Application-1, API1 can be invoked
at a rate of 10 Req/min, API-2 - 1Req/min and likewise. So when a new user
signs in, there'd be a potential increase in the traffic on the API.

As of now there isn't a way to limit the total number of calls made on an
API. Tiers defined at the API Level, doesn't reflect the global limit of
the backend; which means that, as an API keeps gathering users, hits on the
Backend would also keep increasing without being controlled.

With API Manager 1.10.0, the plan is to provide the capability to define
Hard Throttling limits for APIs. The limit will be defined per API basis,
and this usually will reflect the number of requests the actual backend can
handle.

This feature warrants several changes on API Designing UI, and those can be
discussed in detail in mails to follow.

If giving a high level idea about the flow.
1. API creator logs into the publisher and creates an API.
2. API Creator enables Hard Limit throttling for the API.
3. Number of requests allowed and Unit Time is specified.
4. Changes are saved and Published to the Gateway.

When saving the API, a throttling policy specific to the API will be
created and saved in the registry.

For enforcing throttling limit, a new handler will be written, which would
only appear for those APIs on which Hard limit is enabled. The handler
would refer to the policy saved to the registry and would apply the limit
defined.

Please share your thoughts on this.

-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to