Cloudflare Workers
Serverless code that runs on Cloudflare's edge. Where I put the dynamic pieces that a static site can't do on its own.
I’ll be honest, I’m still wrapping my head around Workers. I can’t give you a clean textbook definition of what they are, because I don’t fully have one yet. What I do know is that when I hit something in a project that a plain static site can’t handle on its own, Workers keep turning out to be the answer. So I keep reaching for them and slowly figuring out where they fit.
A few things I’ve actually built as Workers: Mission Control, the cockpit for my whole operating system, is a Worker. I rebuilt my link shortener, mjs.link, and that’s its own little Worker. And when I replaced Senja with my own testimonials setup, the form that takes submissions and writes them into the database is a Worker too. None of those are huge, but they’re the kind of thing that needs to actually run code and touch data, not just serve a page.
My mental split right now is simple: static sites go on Pages, anything that needs to think or store something goes on a Worker. The line between the two is honestly getting blurry and that annoys me a little, but I can’t argue with the results. There are certain jobs where Workers are just the way to go, and I’ve got a handful of them running now.