Cas long as it's getting frequent requests but it's complex in reality
CWorkers run on the same edge machine which handled your original request. There is no affinity to routing to a specific machine which already has your worker running. There is keepalive. Chance of two random connections hitting the same machine and thus getting the same worker is pretty low, espec when it can be any machine at any cf pop. However, keepalive can make it confusing since your browser would keep hitting the same
CIf you're worried about cold starts, CF does a good job of that, taking advantage of the tls handshake to warm up the worker during initial connection, elimating cold starts unless you've got a big worker/a lot of code in global scope
Cbut def don't rely on global scope for anything
Eits not about coldstarts
Eits more about i have templates that i need to serve
Estatic html, css
IWhere did you get these stats from?
Eits his own
E.
CIf you're using KV and you want to measure it's real easy and nothing fancy, just performance.now() and writing to Cloudflare's Analytics Engine, ex:
Then you can use Grafana w/ AE and build nice dashboards relatively easily
Then you can use Grafana w/ AE and build nice dashboards relatively easily
Equick question since you seem like you know the ins and outs. How would you go about serving static content? with wildcard domains
would you just store everything in a r2 bucket, then have a worker in the front responding with the proper files?
would you just store everything in a r2 bucket, then have a worker in the front responding with the proper files?
Cwildcard domains being one of your domains, all subdomains, or as in you'd want to hook up customer domains?
Eboth
EI thought i might get away with doing cd of CF pages
EBut doesnt seem like i can
Cwith the same set of static assets for all, or would customers have different ones or something?
EDifferent
CFor customer domains you need CF For SaaS on top, and you can't do wildcard with CF For SaaS without Enterprise
Cyou could go Workers Static Assets, pay nothing for requests like pages, and use wildcard routes for your own domain
Cthen you can use CF For SaaS easily with plain Workers
Cif you need lots of customer assets though, well you can only have 500 workers even on paid, and there's limits on assets/would be messy to intermingle, you'd probably want to just throw their custom stuff into KV
CKV is 25 MiB max though, per key (just like Pages and Workers Assets)
EI think this is what i need
EWhat about queues
EI will see as the content is statically generated
Cwhat about them?
ECant i offload the workload to them?
EI think 500 workers are more than enough for ~10m requests a day
Cwat
CI was saying 500 workers max as you'd likely want to do a worker per customer, like you would a pages project per customer, if they had all their own assets. But hard with the hard-ish cap on workers
C500 Workers, meaning, only 500 Cloudflare Workers you can create. A Single worker can do a billion requests, not limited in scale, or running location, or anything
EWhy would i do that? Seems like a waste of resources
Cso they can have their own static assets?
Ccan't quite throw a ton of customer static assets into a single worker
EBut i can just throw it into a r2 bucket
CYou could. You pay for those requests though
EHow much?
CCloudflare Docs
R2 charges based on the total volume of data stored, along with two classes of operations on that data:
ELet me see
CGETs are Class Bs, you'd want Frequently Accessed Storage + storage cost
E0.36$ per million reads
CIf you're going Worker, you'd want to use the R2 Binding, and then you'd want to use the Cache API as well. Worth noting any Cache API hits wouldn't cost you anything
Cyea relatively cheap, cheaper then KV at $0.50 per mil
Cstill not cheaper then Worker Static Assets unlimited free requests, plus versioning and such
E:pepethink:
EWould cloudflare let me buy server slot(s) on their data centers?
Ccan't buy vps's or dedi's no, Cloudflare also doesn't own any data centers, merely colocating at existing ones, possible you could colocate at the same location but why
EHmm
EWell my initial plan was to buy server space and my own hardware and run everything on nixos using microvm.nix and firecracker
