1. Developer Experience (DX) is a Mixed Bag
While some users are frustrated with Cloudflare's overall developer experience, others acknowledge recent improvements or find workarounds that make it viable.
"Cloudflare in general is a DX mess. Sometimes it's dashboard doesn't even work at all, and is peppered with error messages." — locknitpicker
"Cloudflare Workers has really improved lately, e.g. 'Observations' and 'Metrics', and on top of that their product suite keeps growing all the time." — l5870uoo9y
2. Language Support and Ecosystem Strategy
There's a debate over language support and how to best integrate with Cloudflare's ecosystem. Some suggest using compiled languages like Rust/WASM for stability, while others advise sticking solely to Workers and avoiding Cloudflare's other managed services.
"I'm building my entire back-end on CF Workers. The DX was really frustrating starting out, but I'm using Rust/WASM, which means most of my issues get caught at compile time. My suggestion: avoid all the CF offerings (DB, Pages, KV, etc.) and stick with just Workers." — csomar
3. Cost-Effectiveness and Scalability
Users are weighing the cost and performance of Cloudflare Workers against traditional hosting (like a VPS). For some, the edge performance is a key selling point, while others question the value proposition for handling high traffic or DDoS attacks.
"I mean the biggest thing that could happen to me is landing on the HN front page and a $5 per month VPS can manage that easily" — huijzer
"If you use Astro[1] together with Cloudflare then you have a solution that is at least on par with NextJS and Vercel, but that only costs a fraction." — l5870uoo9y