is the best way to segregate HTTP access
is the best way to segregate HTTP access for queues to manage secrets within a worker?
eg: client calls a normal worker rest endpoint and passes the secret, then the worker does a switch statement to correctly forward the message to a queue while checking the secret against that queue name using a map?
6 Replies
What is your use-case here? You want to authentificate access to your queues and consume from multiple queues in a single worker?
I am working on a "micro-framework" for Cloudflare Queues, thats why I'm interested in it.
Unknown User•3d ago
Message Not Public
Sign In & Join Server To View
@m0c . How you deal with missing local development support. This is so annoying for me, did you solve it also internally?
Opened a discussion point here: https://github.com/cloudflare/workers-sdk/discussions/7548
GitHub
Enable Cross-Worker Queue Testing Locally · cloudflare workers-sdk ...
Proposal: SQLite-based Queue Implementation for Local Development Background Currently, wrangler's local queue implementation uses an in-memory array for storing queue messages, which prevents ...
GitHub
GitHub - storimi-team/narabi: Elegant queue handling for Cloudflare...
Elegant queue handling for Cloudflare Workers. Contribute to storimi-team/narabi development by creating an account on GitHub.
This is the starting point, I need to spend a bit more time on it as it's super optimized still on my problem statement. Which was not having an elegant way like Hono does for http to route queues and have a context / type based message api.
There should be generic middleware support e.g. concretely for drizzle which I need next, also some shortcuts like naming of queues with env-type handling needs to be configurable.
So far it's just a little helper to standardize the way of implementing workers consumer from multiple queues and separating concerns.