Cloudflare Workers

“Advantage is I use Cloudflare free tier so get denial-of-wallet prevention when my free credits run out.”

“Cloudflare workers pricng is so much more legible, it's one of the reason of their success.”

“you don’t pay for the processing time while you’re waiting for upstream network responses.”

“The design and architecture is extremely minimal to the point that all of it can be explained on a single A4 page”

“you can do a LOT with that. Once you drink the cloudflare kool-aid regarding workers they let you build very scalable apps”

“lets a single developer run crazy projects for insanely cheap and with almost no maintenance”

“I like and appreciate Workers, and am grateful to be paying less because Cloudflare bin-packed more.”

“If you can accept the risk though, you get cheap compute with someone else managing all the infrastructure.”

“For a while the Workers platform didn't satisfy the self-hosted part, but I guess workerd addressed that.”

“So I pay the $5 a month, more than happy to, so it stays free for people and with no ads.”

“It runs on Cloudflare Workers + D1 for DB, it should easily be within their free tier for most use cases.”

“Very difficult to beat if you don't process or store private information that should not be given to the US company.”

“the cf workers runtime is kind of unique and you cannot push there any code without making it cf workers ready in the first place”

“They prefer waiving the occasional DDoS / misconfiguration over giving their customers to cause outages”

“we already use regular CF builds for frontend previews, but that doesnt solve a fullstack PR preview much”

“Cloudflare still haven't shipped the most valuable possible feature for Cloudflare Workers though: hard billing caps.”

“I'm amused that it made me accept the terms and conditions without any indication of who I am, but it did work”

“Your code base finally felt portable to Workers with essentially full CF platform support.”

“isn't cloudflare webworker and email forwarding infra hyperscaling and highly available?”

“enough of our users were in Spain and couldn’t access endpoints at seemingly arbitrary times (due to the matches)”

“plenty of resources, such as workers, don't belong to zones so essentially their code can be replaced or deleted with the lowest level permission”

“where Cloudflare's Nairobi and Mombasa PoPs make a measurable difference over traditional hosted WordPress”

“the runtime and the APIs are apache 2.0 licensed and uses web standards wherever possible”

“Cloudflare's biggest benefit is the wrangler cli which when paired with claude code means that you can completely handoff setup/debugging/analysis.”

“They’ve made deploying and maintaining microservices significantly easier and more cost-effective”

“it's a very good platform. Just missing compartmentalisation features between prod and dev environments.”

“I'm building a commercial SaaS product on Workers. Although I've barely scratched the surface of what Cloudflare offers, so far it's been great.”

“Cloudflare letting the LLM write a single JS function to execute the whole chain in an edge isolate is super smart.”

“The approach of tracking usage locally and cutting off before you hit billing overages makes a lot more sense than trying to parse the billing API after the fact.”

“last few months has been quite rough for Cloudflare, and a few outages on their Workers platform that didn't quite make the headlines too”

“I really like CF approach to cloud, it's a nice middle ground between old school heroku and full fledged AWS”

“Workers don’t belong to zones, so you can’t scope a particular user or API key access to a particular set of workers”

“The main value proposition of Cloudflare Workers is being able to deploy workers at the edge and use them to implement edge use cases.”

“I always liked CF workers but haven't shipped anything serious with it due to not wanting vendor lock-in.”

“with Workers they're accessible from hundreds of locations around the world so you can get this sort of speed from almost anywhere”

“There's something really nice about not needing to patch anything for years because all you're using is the Python stdlib and scaling from zero to many, many thousands with no added effort.”

“when you build on Workers, you are not tied to one provider, because you can run workerd anywhere”

“We deliberately avoided them in the critical path because we knew we'll have to setup multi cloud”

“worked well enough... having each email address target have to approve themselves was about the only hiccup”

“the workers model could be great for handling relatively short lived tcp connections, not just web requests”