Chang
CDCloudflare Developers
•Created by Chang on 11/12/2024 in #workers-help
Workers concurrency
Maybe a dumb question but I tried to learn about concurrent requests to workers - when documentation says only one instance of the worker in a edge server, how will it handle let's say we get 100 requests concurrently to the same edge server? How are memory limits handled? Will it span more workers in the same edge location or it will reject the requests if the instance is already beyond 128mb. Are cancelled requests retried? I am a bit lost trying to understand this topic even after a lot of research into Cloudflare forums also.
How do we plan for concurency? GCP Cloud Run offers it as a configurable parameter for each instance of the container.
1 replies
CDCloudflare Developers
•Created by Chang on 2/17/2024 in #workers-help
workers site caching and DDoS
I am kind of new to CF. I have a workers site that renders static HTML for any subdomain using the route *.mydomain.com. It works fine as expected.
Now I am unable to figure out how to enforce caching on the generated HTML so that the Worker won't be hit every time until the cached HTML is purged explicitly or CF removes the cached page.
I am more worried about getting DDoS-ed. I am implementing a simple static site builder using CF Worker site as the origin and using Cloudflare SaaS for custom domains.
I understand I can upgrade to Business/Enterprise and have better DDoS options. But I am wondering how are small companies dealing with unexpected large unexpected Workers bill.
Edit: Small typo
3 replies