Do you consider your service high-load? Can you explain with numbers?

A high-load service is a service that processes a large number of requests or data per unit of time, requiring scaling and resource optimization.

To assess whether a service is high-load, specific metrics can be used:

• Requests per second (RPS): for example, the service processes 10,000 requests per second.
• Number of concurrent users or connections: for example, 50,000 active users simultaneously.
• Volume of data processed: for example, the service reads and writes 1 TB of data daily.
• Delays and response time: for example, the average response time is 50 ms under such load.
• Resource utilization: CPU is 80% loaded, memory is 70%.

If your service operates with such or higher metrics, it can be considered high-load. It is also important to consider requirements for fault tolerance and scalability.

Example: "Our service processes an average of 15,000 requests per second with peak loads up to 25,000, and the average response time does not exceed 100 ms, which requires clustering and load balancing."