Anyone running an API that can be reached by the outside world should most definitely be concerned that someone might pummel their server by making a massive amount of requests to that one endpoint that requires a bunch of on-the-fly calculations. Enter Django Rest Framework's throttling. It allows you to easily configure the framework to stop allowing requests from a user once they've made so many requests in a period of time. Whether you're concerned about requests over a sustained period of time or in short bursts, rate limiting with throttles will handle it.
However, there are times you might need to limit based on something less consistent than number of calls per minute or day. One example we we ran into was clients submitting requests for a process that requires a lot of human work to complete, and the possibility that a large number of these requests might mean that the client doesn't actually understand the real purpose of the feature, or an indicator of a bigger problem for that client. If you can limit these clients to a certain number of outstanding requests at any given time, this allows for the time for our client contacts to process the appropriate requests or contact them if the requests are inappropriate.
While the throttles provided by Rest Framework are all about rate limiting, writing a custom throttle to do this is pretty simple.
### throttles.py from django.db.models import Count from rest_framework.throttling import BaseThrottle from rest_framework.exceptions import Throttled from .models import Inspection class InspectionThrottle(BaseThrottle): def allow_request(self, request, view): inspections = Inspection.object.filter(client=view.client) if inspections < 15: return True raise Throttled(detail=( "You have reached the limit of 15 open requests. " "Please wait until your existing requests have been " "evaluated before submitting additional disputes. ")) ###views.py class InspectionCreateView(CreateAPIView): model = Inspection throttle_classes = InspectionThrottle
By simply defining an
allow_request method you are free to use whatever logic you want to throttle requests, so long as you return
True to allow the request and raise the
Throttled exception to deny the request.
Throttled also accepts a kwarg of wait which will set the
X-Throttle-Wait-Second header for notifying the client how long to wait before trying again. This is mostly just useful for rate limiting, but maybe you'll be clever and have a reason to use it.