Relatively new to workers though also a relatively senior dev (rails). I have a couple questions tha
Relatively new to workers though also a relatively senior dev (rails). I have a couple questions that itch at the back of my mind and I just wanna make sure I'm understanding things right.
- Static Assets can nominally support queue consumers but I'm a little unclear on what that implies, does it mean that the main worker can define a single push consumer? I'd assume that kind of has to be it, right, it doesn't seem possible to have multiple push consumers since the consume method doesn't declare anything about from which queue it consumes. It, like me on a good costco sample day, just consumes. Is the idea that, if you want to build a consolidated full stack app with multiple queues, you'd use this strategy for one consumer processing multiple queues?: https://developers.cloudflare.com/queues/reference/how-queues-works/#consumers
- Conceptually, when using a framework with Static Assets, are SSR endpoints and SSR components de facto micro deployments of individual workers? I guess this is as much a question about how the adapters work. For example, if I have an Astro endpoint file that handlers multiple HTTP verbs, are those functionally translated into separate workers, or maybe more likely a single worker that happens to have Astro-specific syntax to handle the different request types? Is this analogous to how Pages Functions worked? How literal is this, like, were PFs ultimately run on individual isolates? My apologies if none of this makes sense, I'm asking out of curiosity from a sort of half formed shower thought involving leveraging the ephemeral nature of global scope in workers to emulate some architectural stuff that is laid out in the blog posts about how Waiting Room works.
Cloudflare Docs
Cloudflare Queues is a flexible messaging queue that allows you to queue messages for asynchronous processing. Message queues are great at decoupling components of applications, like the checkout and order fulfillment services for an e-commerce site. Decoupled services are easier to reason about, deploy, and implement, allowing you to ship featu...
