Rate Limiting helps maintain performance, security, and system stability by limiting requests made to your application within specific rules. These settings allow you to control excessive requests from the same client, IP address, or user.
Kuika provides Rate Limiting configurations under the Configuration Manager module via App Settings.
Accessing Rate Limiting Settings
Log in to the Kuika platform.
Select the project you want to work on from the Apps screen.
Click on the Configuration Manager module in the left menu.
Open the App Settings tab.
Under the Rate Limiting heading, use the ADD NEW option to create a new rate limiting definition.
Rate Limiting Configuration
When creating Rate Limiting settings, the following fields are configured:
Name: Used to identify the created rate limiting rule. This field is required and ensures that the configuration can be distinguished.
Enable Rate Limiting: Determines whether the rate limiting rule is active. When the switch is on, the defined rules are applied.
Rate Limit By: Determines the criterion by which requests are limited.
Supported options:
IP: The limit is applied based on the client's IP address.
Client ID: Limits are applied based on the Client ID. This field is mandatory.
General Rules
In the General Rules field, the maximum number of requests for specific time intervals is defined. Each rule consists of the following two parameters:
Period: Specifies the time interval for which requests will be counted.
Examples:
10s → 10 seconds
1m → 1 minute
1h → 1 hour
Limit: Defines the maximum number of requests that can be made within the specified time interval. Multiple rules can be added to define separate limits for different time intervals. The Add rule option can be used to add a new rule, and existing rules can be deleted with Remove.
Saving Rate Limiting Settings
After filling in all fields and defining the rules, you can save the rate limiting configuration by clicking the CREATE button.
The created configuration controls request traffic across the application, ensuring:
Prevention of overload
Secure and balanced traffic management
Consistent limiting independent of the environment (dev / test / live).
