Introduction​

Let's start with an exciting use case. You have implemented your big idea and created a fascinating website or mobile app, and you are ready to tell the world about how cool your app is. Everything went well, everyone wants to use your app. Then suddenly your backend starts to reject new registers because it receives more requests than it can handle. First of all, good for you, it looks like you built a product that people want to use. Secondly, shame on you, because you didn't test the maximum concurrent requests capacity of the backend.

Introduction​

In this article, we will demonstrate how to use the Ddosify GitHub Action to periodically test the latency of our target endpoints from 60+ cities worldwide. By configuring the action to run on a schedule, we can ensure that the performance of our locations is consistently monitored. If the latency of any of our locations exceeds the expected value, we will receive an email notification alerting us to the issue. By using this action, we can proactively identify and address potential performance issues before they impact our users.

What exactly is latency in telecommunications? The time it takes for a set of data to travel between two points on a network is referred to as “network latency." The low latency of 5G technology makes it very different from previous generations of mobile network technology.

Introduction​

In this article, we will write an endpoint using the Django REST framework with API Key throttling (rate limiting). We will first use Django default cache configuration Local Memory Caching for throttling and we will see that this method does not work for multiple workers on gunicorn or multiple replicas on Kubernetes. We will change the Django cache configuration to Redis to solve this problem. We will test throttling with the open-source load testing tool Ddosify.