You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first of all: It is a pleasure developing for CF Workers thanks to your amazing local tooling with miniflare in it's core. Thank you very much!
Now it comes to the dark sides of local simulation: The Cloudflare Platform Limits ( https://developers.cloudflare.com/workers/platform/limits/ ).
On a recent project we developed for some weeks locally until the Worker did what it should. It is kind of a Data Warehouse Data Collector based on D1, Workflows, Cron Triggers, Queues and the latest versions of the Worker Platform.
Locally everything worked out perfectly fine. We were happy. Amazing solution with great performance building upon nice tools provided by the CF Platform. Great DX :-)
Then we deployed it to Cloudflare ... and we faced "reality" ... . The Worker was unable to perform as it should due to "API request limits". It runs on Workers Paid. So 1000 requests seems "a lot". But it's not. As each D1 DB call is part of the limit...
I would not like to discuss the limits, but asking for a way to know of these limits while developing locally. As we tested locally with exactly the same data base we now want to run on prod, we passed the limits there as well already.
A warning, note or whatsoever would be a massive support to know as early as possible that the app that works locally will not do so after being deployed.
We now need to fundamentally change core parts of the app to facilitate less requests. Knowing that before would have helped us to reduce frustration and developing costs now at the latest possible time of the dev cycle.
Best Regards,
Jan
The text was updated successfully, but these errors were encountered:
Hey there,
first of all: It is a pleasure developing for CF Workers thanks to your amazing local tooling with miniflare in it's core. Thank you very much!
Now it comes to the dark sides of local simulation: The Cloudflare Platform Limits ( https://developers.cloudflare.com/workers/platform/limits/ ).
On a recent project we developed for some weeks locally until the Worker did what it should. It is kind of a Data Warehouse Data Collector based on D1, Workflows, Cron Triggers, Queues and the latest versions of the Worker Platform.
Locally everything worked out perfectly fine. We were happy. Amazing solution with great performance building upon nice tools provided by the CF Platform. Great DX :-)
Then we deployed it to Cloudflare ... and we faced "reality" ... . The Worker was unable to perform as it should due to "API request limits". It runs on Workers Paid. So 1000 requests seems "a lot". But it's not. As each D1 DB call is part of the limit...
I would not like to discuss the limits, but asking for a way to know of these limits while developing locally. As we tested locally with exactly the same data base we now want to run on prod, we passed the limits there as well already.
A warning, note or whatsoever would be a massive support to know as early as possible that the app that works locally will not do so after being deployed.
We now need to fundamentally change core parts of the app to facilitate less requests. Knowing that before would have helped us to reduce frustration and developing costs now at the latest possible time of the dev cycle.
Best Regards,
Jan
The text was updated successfully, but these errors were encountered: