Content Comparison

Tip
The Framework proposed in this space (Alex Xu) is applied to propose a design : Getting started - a framework to propose...

Introduction

The benefits of using an API rate limiter :

Prevent resource starvation caused by Denial of Service (DoS) attack, either intentional or unintentional, by blocking the excess calls.
Reduce cost by limiting servers and allocating more resources to high priority APIs. Important when we use paid third party APIs.
Prevent servers from being overloaded by filtering out excess requests.

on this page.

Table of Contents

Type of rate limiter ? client-side or server-side ? Or in a middleware ?	Server-Side or Middleware
Rules of throttle ?	Different sets of throttle rules (IP, user ID, etc.)
Scale of the system ? Small, Medium, big company	Big company
In a distributed environment ?	Yes.
Implemented as a separate service or in application code ?	No matter.
Inform user who are throttled?	Yes.

limit excessive requests
low latency - not slow down http response time
limit the use of memory as possible
can be shared across servers and processes
exception handling - show clear exceptions to users
high fault tolerance - if rate limiter goes offline, it does not affect the system