참조: https://community.apigee.com/questions/35903/what-is-main-difference-between-quota-policy-and-s.html

1. Quota Policy: This policy is used to meet up the business requirements where business decides the no. of calls allowed for a product/developer/developer app etc and also they can decide pricing for different products based on no. of calls allowed. This ensures business that no developer/app can make calls more than the allowed limit.

2. Spike Arrest: This policy is used to avoid spikes in traffic and protect your backend systems against spikes so I will take it as a measure to protect/secure your API.


01. Quota Policy : It defines a time window ( for example 1 hour or 1 minute ) and within that time a fixed number of request are honored. For example, in 1 hour 10 requested are allowed and the user is free to make all the 10 request in 1 second or 1 hour. The basic idea is that only 10 request are allowed in an hour and make sure a user can make a fixed number of request

02. Spike Arrest. This policy specifies the total number of request and divides between the time interval that is defined. If the number of request is more then that calculated amount that the policy will block access. The idea behind is to make sure the traffic that is coming to the server or handled by target system is smooth and sudden burst of request does not impact.performance.


Quota Policy helps you limit the number of requests per time interval. For instance, setting quota policy rate to 10 per minute, it is possible to hit all 10 requests in the first few seconds of a minute.

Spike Arrest Policy, on the other hand helps you limit the sudden increase in the number of requests at any point in time. For instance, setting spike arrest policy rate to 10 per minute, it does the following calculations to limit the sudden spike/increase in the number of requests -

10 per minute = 10 per 60 seconds = 1 per 6 seconds 

It will not allow more than 1 request every 6 seconds. In this way, we can ensure that all 10 requests are not made within the initial seconds of a minute.

Spike Arrest Policy helps in reducing the risk of automated request generation through malicious code.

The examples are well explain in the Apigee Documentation -

Quota Policy

Spike Arrest Policy

'TF' 카테고리의 다른 글

[Research] django high availability  (0) 2017.06.28
[Research] openstack  (0) 2017.06.27
[Research] 스파이크( spike)  (0) 2017.06.27
[Research] API (Application Programming Interface)  (0) 2017.06.27
[Define] TF 란?  (0) 2017.06.27

+ Recent posts