Built a blogging platform on Cloudflare Workers - lessons learned
Spent 6 months building a blogging platform (justblogged.com) and wanted to share some tech decisions that worked (and didn't).
The Stack:
- Cloudflare Workers for edge compute
- D1 (SQLite) for the database
- R2 for image storage
- Global CDN for static assets
- Custom domain routing via Cloudflare + Reverse proxy (VPS)
What worked well:
- Edge deployment = consistently fast (<500ms) globally
- Workers pricing scales nicely with usage
- D1 is surprisingly capable for this use case
- Zero server management headaches
What was harder than expected:
- Custom domain SSL automation
- Richtext editor that fits well with this
Current status:
- ~20 users, free tier
- Costs: ~$8/mo currently
Many devs have (or should have) their own personal blogs/websites. You can use justblogged.com for that please :)
Trending on Indie Hackers
Nice post — building on Workers is a powerful pattern, but the real proof is often in how edge cache behavior, data consistency, and function invocation patterns interact under load.
In many edge-first builds I’ve seen, the first signal that surfaces real trade-offs isn’t raw latency — it’s cache invalidation churn and how frequently you accidentally serve stale content or burn through invocation quotas when invalidating aggressively.
Curious — in your lessons learned, which metric or behavior ended up dictating architecture decisions most strongly (e.g., cache hit ratio, KV read/write latency, or function invocations per user action)? That usually tells engineers where the real constraints are.