Restrictions in Kuroco
Restrictions in Kuroco
Explaining the restrictions in using Kuroco.
Contents
ID
- IDs such as topics_id are automatically assigned and may not start from 1 due to the specification of inheriting data from the account creation source.
Number of Contents
- topics_id takes values from
1
to2,147,483,647
. In theory, it is possible to register up to 21 billion contents, but we have not verified the operation with that many contents. Depending on the data items, performance is expected to be within 1 million records. Please consult with us if you plan to use more than that.
Order
- Values that can be entered for ordering are up to 9 digits.
API
Concurrent Connections
- There is a limit on the maximum number of concurrent connections to the API, and exceeding the limit will result in a 429 error.
- For API access without caching: Maximum concurrent connections per hostname: 200
Assuming an endpoint that takes 300ms to respond, receiving more than 200 requests within 0.3 seconds, most customers will not reach the limit. - For cached API access: No limit on concurrent connections
- For API access without caching: Maximum concurrent connections per hostname: 200
Query String
- The maximum length of the Query String is around 8000 characters.
Files
Kuroco Files
The maximum file size that can be uploaded to Kuroco Files is around 80MB.
If you want to upload files larger than 80MB, consider integrating with GCS or S3.Please check the file types that can be used in the file manager.
Kuroco Front
- The maximum file size that can be uploaded to Kuroco Front is 30MB.
Support
If you have any other questions, please contact us or check out Our Slack Community.