Hello,
I am trying to implement rate limiting for certain API Products
that I plan on exposing to my customers. For instance, I have 3 Products
with the same proxies.
Product A - 10 calls/min - 100 calls/month
Product B - 20 calls/min - 10,000 calls/month
Product C - 30 calls/min - 100,000 calls/month
However, there seems to be a slight disconnect between what I see
in common API pricing models and the Apigee documentation. This could
easily be down to my lack of understanding and hence this post. See Zendesk's or Slack's per minute rate limits. Now my questions (specifically around the calls/minute aspect):
(1) Are these per minute rate limits in place due to business
considerations (i.e. a means to force customers to move higher)? Or are
they meant to be means to protect backend systems from sudden traffic
spikes?
(2) What Apigee policy is more suitable to achieve the above
mentioned configuration (of 10, 20 and 30 calls/min) - Spike Arrest
policy or Quotas? To me it seems Spike Arrest as there is a line here that mentions Quota is better suited for longer intervals such as days or months. Is this correct?
(3) If its spike arrest, does the policy have to be defined at a
Product level? This way all API developers of a given tier are entitled
to the same number of calls/minute.
(4) Can there ever be a situation where a quota can conflict with a spike arrest policy?
Please let me know.
Thanks
LinkedIn
Twitter
