Apigee 4MV4D - API Traffic Management : Quota - Series - Quota Policy - S02E02

[anilsr]

Hello Apigeeks,

In this 4MV4D video, We will see how to apply quota on API using Apigee Edge Quota policy. Apigee Edge Quota policy can be configured for more dynamic quota management. We will see same in upcoming 4MV4D videos.

Apigee Edge Quota Policy allows you to define number of API calls that can be allowed in defined interval of time inside policy code. Find the Quota Policy used in above 4MV4D video for your reference below,

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Quota async="false" continueOnError="false" enabled="true" name="QP-QuotaDemo">
    <DisplayName>QP-QuotaDemo</DisplayName>
    <Properties/>
    <Allow count="3"/>
    <Interval>1</Interval>
    <TimeUnit>minute</TimeUnit>
</Quota>

As you can see above, Above policy code defines Quota of 3 API calls per minute.

<Allow> xml element is used to define number of API Calls. <Interval> xml element is used to define interval of time for quota calculation & <TimeUnit> to define frequency time unit. For possible values, refer policy documentation here.

You might have observed in 4MV4D, More than 3 calls are allowed within a minute although we have specified 3 per minute. It's due to number of message processors & counters sync between them. Policies gets executed in message processors & by default Apigee Edge org comes with 2 message processors. That's the reason we have seen more than 3 api calls. As you might have noticed after 6 calls all other calls returned 500 error within a minute where API is terminated at Apigee Edge layer. We will see more about how to sync counters between message processors in upcoming 4MV4D.

4MV4D videos are completely focussed on API Developers & Help you learn many interesting concepts very quickly using hands on approach. Don't forget to subscribe to channel here. Feel free to send your feedback/queries using comments below or Ask a question if you have any query. Stay tuned for more videos.