Which is the max amount of concurrent requests a custom web service is able to handle in Creatio?
Hi, I would like to know if there is a max amount of concurrent requests that Creatio is able to handle for custom web services defined in Creatio.
Is there any way to configure the max number of allowed concurrent requests to the same service on the technical user, the web service or the package containing the web service?
Like
Hello,
There is no configurable maximum number of concurrent requests setting in Creatio for custom web services. The idea of a fixed limit isn't practical, because the performance impact of a request depends heavily on what the request actually does.
For example:
- 1k lightweight requests that perform simple data retrieval or write operations may have minimal impact on the system.
- Conversely, 1k complex or resource-intensive requests (e.g. involving multiple joins, integrations, or heavy business logic) could significantly degrade performance or cause failures under load.
Instead of a static limit, Creatio relies on the underlying infrastructure and available resources to dynamically manage the load. When system resources become constrained, the platform will naturally slow down or reject excess incoming requests to protect stability.
We recommend using a batching approach when integrating or calling custom services:
- Start with batches of 2,000 to 20,000 requests, depending on the expected load per request.
- Perform load testing to evaluate how the system responds. If the particular request is lightweight, you can safely increase the batch size.
This approach gives you flexibility and scalability without setting limits that may not reflect actual usage.
Hello,
There is no configurable maximum number of concurrent requests setting in Creatio for custom web services. The idea of a fixed limit isn't practical, because the performance impact of a request depends heavily on what the request actually does.
For example:
- 1k lightweight requests that perform simple data retrieval or write operations may have minimal impact on the system.
- Conversely, 1k complex or resource-intensive requests (e.g. involving multiple joins, integrations, or heavy business logic) could significantly degrade performance or cause failures under load.
Instead of a static limit, Creatio relies on the underlying infrastructure and available resources to dynamically manage the load. When system resources become constrained, the platform will naturally slow down or reject excess incoming requests to protect stability.
We recommend using a batching approach when integrating or calling custom services:
- Start with batches of 2,000 to 20,000 requests, depending on the expected load per request.
- Perform load testing to evaluate how the system responds. If the particular request is lightweight, you can safely increase the batch size.
This approach gives you flexibility and scalability without setting limits that may not reflect actual usage.