but i get a warning abt cloudflared when running a normal apt update anyway lol

is anyone aware of a documented workers limitation when using custom subdomains that causes 503 origin errors? for example: - subdomain.example.com is in CF DNS, but as NS records that point to google dns, that has an A record pointing to a load balancer - someworker.example.com is a CF Worker. when someworker makes a request to subdomain.example.com from a custom subdomain, this will 503. if you access the workers.dev route for the worker, it will work. in this same exact scenario, if the subdomain.example.com was set to a wildcard in google dns and you accessed nested.subdomain.example.com, this will resolve. is this documented anywhere or any other suggested workaround (other than changing to an A record)? 😓

At my external service with database, I have table

Student(id, name)

. User can change student info. Is it a good idea to add an extra field

Student(id, seed, name)

where

seed

changes every time

name

changes. Then in my worker, I can do:

ts
fetch(`${API}/student/${id}/seed/${seed}`, { cf : { cacheEverything: true } })

So that I can cache student record indefinitely without worrying about stale data 🤔

Oh. I can just use the

updatedAt

instead of

seed

.

Please let me know your thoughts 👍

hey im getting but i have nodejs_compat flag

bot:dev: [mf:err] VMScriptRunnerError [ERR_MODULE_RULE]: Unable to resolve "dist\worker.mjs" dependency "node:events": no matching module rules.
bot:dev: If you're trying to import an npm package, you'll need to bundle your Worker first.

also I need a little advice. I'm making a serverless discord bot, and I have a /setup command that sends a message with a select menu. In discord.js I could then use

interaction.awaitMessageComponentInteraction

but in this case I can't. I was thinking of making my own such function that would listen for an EventEmitter that would be global, but I'm not sure if that's the best solution. Because I want to have everything in one function, and I don't want to separate it in any way. If you have any ideas, I'd certainly be happy to.

Can I use workers as the only backend of my app? I don't need much data storage, so it seems like it should be fine, but I'm having trouble figuring out what parts (if any) are actually persistent, and what parts are deleted when no longer in use. For example,

durable objects

sounds very persistent to me, but apparently they get thrown away if not in use?

possible.

it depends on what tech do you need in your backend.

The response would be in a complete different request, so you would have to handle it separately

I need to store small json objects. No computation other than access rights.

If they are small enough, you can just inline them directly into your Worker

as long as no hanging connections that require pre-processing or post-processing by worker 👍

Sorry, I don't understand either of your responses. I want a "server" that can expose a rest api or websocket, and read/write json objects. What's pre/post processing here? And inlined json objects would be static, no?

Oh you want dynamic. The REST API can be a Worker with a router. WebSockets are best handled in a Durable Object. JSON objects that don’t change very often can be stored in KV

I was unclear. I mean, as long as it fit worker limits 🐸

"that don’t change very often" how often is very often? Should I use something else for this storage?

If you need it to update multiple times per minute, then it might not be the best choice

I feel super novice here. Are people using workers for anything other than caching in front of an existing backend, hosted outside of cloudflare?

Yes. You can host entire websites on them. You can use them for security, form validation, logging, caching, interactions with databases, and many more applications

Cool. I couldn't find an example showing a super simple data storage api hosted only on cloudflare. I looked through all the examples at https://developers.cloudflare.com/workers/examples/ Am I missing something obvious?

I have small image uploader using CF workers

But it's not probably what you want

it sounds fairly close to what I want

if I can also upload json somewhere, it'd be what I want 🙂

is there any other way to make the response faster and not too laggy?

export default {
  fetch(req) {
    const url = new URL(req.url);
    url.hostname = 'exampledomain.com';

    return fetch(url, req)
  }
};

The only 'slow' part of that is waiting for the origin

Whatever domain you're actually fetching, so if you can make that faster, your worker will be faster

so the worker is depending on the domain?