-
Hi, Is it ok to build features like this? Will your Cloud handle it all well (queue request as it needs) or there is risk of errors? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
This is a great question. Wondering as well, if their Cloud will be handle requests from a NextJs application, where thousands of pages, are generated statically at build time. |
Beta Was this translation helpful? Give feedback.
-
Hello, Let me provide some insights:
To sum it up: While you can certainly build features to use multiple parallel calls, it's essential to understand the underlying limits and mechanisms to ensure smooth operation. Always monitor for '429' responses and adjust accordingly. Please be aware that this applies to our paid subscriptions and earlier free plans. The "developer sandbox" plan comes with significantly reduced limits. In the future, we anticipate differentiating the limits between the "hobby" and "pro" plans. |
Beta Was this translation helpful? Give feedback.
-
When I need to remove and create multiple entities with the same relation I can do it from mutation of the related entity (all in one request):
@matej21 Do you recommend to do it like this when possible, or it is better to remove and create entities one by one directly? |
Beta Was this translation helpful? Give feedback.
Hello,
Let me provide some insights:
Hard limit on Nginx level: Our infrastructure employs two nginx instances. Each instance is set up to allow 50 requests per second for your project, so in total, you're looking at 100 r/s. Importantly, nginx's
limit_req
directive is set with parametersburst=200
anddelay=60
. This configuration allows for brief spikes in traffic – any excess requests beyond the rate limit will either be buffered and slowed down to fit within the allowed rate.Handling Rate Limits: When the rate limit is exceeded, the system will return a '429' status code. This indicates you've reached the rate limit and should adjust your request frequency.
Query Complexity Matters