I think you can argue this both ways. If we look at how things were before - there was no cache, all

I think you can argue this both ways. If we look at how things were before - there was no cache, all requests hit the worker - that’s not quite true now. There is another mechanism now, with static assets, that means your worker won’t be hit. Whether it’s KV or otherwise is an implementation detail, imo.

AAshley I think you can argue this both ways. If we look at how things were before - the...

Chaika•9/30/24, 6:43 PM

You can say not all requests will result in worker invocations sure, still no cache though

Chaika•9/30/24, 6:44 PM

if you wanted to be more specific you could say no cache of worker results but ehh the fact KV internally talks to cache service is an implementation detail

AshleyOP•9/30/24, 6:51 PM

That’s fair, I think this is probably a Cloudflare-specific case where it’s a little cloudy (excuse the pun) - as if I was storing something in KV as part of my Worker, I’d say KV is caching, same as Redis in a non-CF architecture. But with CF having so many caching mechanisms, perhaps it’s better to be explicit and say KV rather than cache for Static Asset workers - thanks for the chat, fun to discuss these things

AAshley That’s fair, I think this is probably a Cloudflare-specific case where it’s a li...

Chaika•9/30/24, 6:55 PM

I mean to me the root of it is just that even if you use kv in your worker you can't cache your worker result and avoid an invocation. Static Assets are entirely free, kv cache hit or not

Mmono_cron So I'm looking at the workers KV docs and I see no way to perform bulk operation...

Chaika•9/30/24, 6:57 PM

not possible via binding atm although it's been requested a fair few times

CChaika I mean to me the root of it is just that even if you use kv in your worker you c...

AshleyOP•9/30/24, 6:58 PM

I agree, but it's not the same as it was before - before it was all workers, every single request, and that's just the distinction that I think is important/needs to be clear. KV, imo, is a form of cache, so I think it's fair to say that for static assets, they are not invoking your worker, and they are (potentially) being returned from cache (which is KV, so you can't control the cache unlike other cache products). What I was getting at with the cache stuff is within Cloudflare specifically there's a lot of heavy-lifting done by the word cache (tiered, reserve etc.) versus in general software engineering, it's a pretty generic term (e.g. you could cache in memory and you're caching, in say a Rails app)

Chaika•9/30/24, 6:59 PM

yea it's def not same as before. With Pages you could even cache function results (or double cache static) on custom domain if you wanted as well which was interesting

AshleyOP•9/30/24, 7:00 PM

I think there used to be a diagram somewhere but I can't find it that explained all the caches, where they sit, and the order of execution - maybe it was on a blog. If someone has an up-to-date version of that, that'd be mega handy (including this new stuff with static assets workers)

AAshley I think there used to be a diagram somewhere but I can't find it that explained ...

Chaika•9/30/24, 7:00 PM

explained all the caches?

Chaika•9/30/24, 7:01 PM

There's general request flow chart but I've never seen anything about all the caches I don't think

AshleyOP•9/30/24, 7:01 PM

Maybe I dreamt it

Chaika•9/30/24, 7:01 PM

really not that many anyway unless you want to try to get deep into dns cache/workers being kept warm/etc

AshleyOP•9/30/24, 7:02 PM

Do you have a link to that general request flow chart by chance?

Chaika•9/30/24, 7:02 PM

right side of specific dash pages like waf if you have big enough of a screen

AshleyOP•9/30/24, 7:03 PM

Thank you

Chaika•9/30/24, 7:03 PM

https://blog.cloudflare.com/building-cloudflare-on-cloudflare/ there is some other diagrams from blogs like

Chaika•9/30/24, 7:05 PM

oh actually there is flow charts for the tiered caches https://blog.cloudflare.com/introducing-cache-reserve/, if you want to include all of the different types of the normal http caches it gets more complex, like
Local -> Tiered Cache Middle -> Tiered Cache Upper -> Cache Reserve -> Origin
and then if you want to get really complex I believe Cache Reserve lives in Pingora while local (and maybe tiered cache too?) just live in other more local services, one of the reasons why cache api is local only afaik

AshleyOP•9/30/24, 7:07 PM

This is awesome, thank you!

Chaika•9/30/24, 7:10 PM

yea there is a lot of layers of http cache, and the rest is more messy. KV is local/tiered. Workers Cache API is just local. R2 Custom Domains just local too, probably same thing for Pages Custom Domains but I've never checked

Chaika•9/30/24, 7:12 PM

yea might just be a general cf for saas thing

DiamondDragon•9/30/24, 7:21 PM

any chance someone can take a look at this? it was reported before and a fix was deployed so not sure why i am experiencing this issue

workers-and-pages-helpError on remote worker: APIError: A request to the Cloudflare API

o7•9/30/24, 7:35 PM

is there a way to get 1 worker to run on GET requests and another worker to run other methods? (not via custom routes either)

o7•9/30/24, 7:38 PM

ra•10/1/24, 1:05 AM

Hi all, I'm using workers and would like to work around the "Simultaneous outgoing
connections/request" limit. Am I able to invoke another worker via service bindings to fan out the requests across multiple workers?

Rra Hi all, I'm using workers and would like to work around the "Simultaneous outgoi...

Cyb3r-Jak3•10/1/24, 1:08 AM

You can not.
From https://developers.cloudflare.com/workers/platform/limits/#simultaneous-open-connections

Simultaneous Open Connections are measured from the top-level request, meaning any connections open from Workers sharing resources (for example, Workers triggered via Service bindings) will share the simultaneous open connection limit.

Cloudflare Docs

Limits | Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

CCyb3r-Jak3 You can not. From https://developers.cloudflare.com/workers/platform/limits/#sim...

ra•10/1/24, 1:14 AM

I submitted a request to raise my limit, but never heard back. Has anyone had success in lifting this limit?

Rra I submitted a request to raise my limit, but never heard back. Has anyone had su...

Cyb3r-Jak3•10/1/24, 1:15 AM

I'd imagine not.

Rra I submitted a request to raise my limit, but never heard back. Has anyone had su...

Isaac McFadyen•10/1/24, 1:21 AM

I believe (not completely sure but highly likely) that the limit is Cloudflare-wide, meaning it's an underlying limit that is built into the Workers runtime and not a limit that can be easily increased per customer.

IImJasonH I'm interested to try out containerized apps on Workers. The [blog post](https:/...

Isaac McFadyen•10/1/24, 3:08 AM

Unless you have an Enterprise contract that specially permits them, containerized apps aren't currently available for Workers.

Isaac McFadyen•10/1/24, 3:09 AM

The blog post was more a "here's this internal thing we're testing out now that might eventually come to external customers" and less "you can deploy containers to Workers right now"

BC17•10/1/24, 9:55 AM

Feel I've searched and there's different responses and levels of understanding on cache reserve and tiered caching, especially when workers are considered so I just want to clarify

If I am serving a SSR site with workers and static assets, would the following occur;

I cache HTML via origin headers (Astro.header.set) on a short TTL, 15 minutes for example. Would tiered caching ever be utilised here if it was switched on?
If I switch on cache reserve, would the static assets served from the public and _astro directories ever be served from it?

The cache reserve is so we can persist assets across deployments due to stale HTML referencing old assets - maybe this is less so an issue, but feel we seem to get stung by all hosts in this department so having some sort of persistent storage between deployments is useful

Ohad•10/1/24, 9:57 AM

How can I acess KV from Cron worker? ScheduleContextScheduleContext seem to be missing kv field

Ohad•10/1/24, 9:58 AM

oh nvm, via Env

felixv•10/1/24, 12:00 PM

Is there some timeline on when Workflows might launch? Is it more weeks or months away? I was hoping this would be launched during launch week but sadly no

arch•10/1/24, 2:10 PM

Anyone using Zig to run Workers with WASM?

Murder Chicken•10/1/24, 3:31 PM

Is it possible to add some kind of context variable when making RPC calls so that I can consume that from within the WorkerEntrypointWorkerEntrypoint methods? I'm trying to avoid having to pass context variable into every method in the WorkerEntrypointWorkerEntrypoint.

Ggotfredsen I think I read the Cloudflare blog post about container support 10 times until I...

Hello, I’m Allie!•10/1/24, 4:20 PM

This one? https://forms.gle/msrkBLBYNFFYRaqY8

Google Docs

Cloudflare Container Platform — Early Access

w3bcode•10/1/24, 4:31 PM

can someone suggest me a good library for loggers like pino but which will work on cloudflare workers/pages

joshka•10/1/24, 4:46 PM

Is it possible to add a tower_http::trace::TraceLayertower_http::trace::TraceLayer to a worker somehow? In normal non-wasm axum I'd just add .layer(ServiceBuilder::new().trace_for_http()).layer(ServiceBuilder::new().trace_for_http()), but when running with cloudflare I get the unhelpful (seemingly impossible to debug) error:

✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

✘ [ERROR] A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

joshka•10/1/24, 4:47 PM

(I say impossible because the stacktrace points at a minimized file)

Cconnor Hey! Our company has been migrating our currently Pages/Workers mono repo to run...

texan•10/1/24, 7:00 PM

Hey Conner, thanks for the feedback! I do know that preview URLs should be available for each version of your worker, though I'm not sure about DOs like you mentioned. Happy to pass this feedback along.

I think you can argue this both ways. If we look at how things were before - there was no cache, all

Similar Threads