Astro blog website histed on cloudflare need to fix R2 issue or host on other alternative - READ DESCRIPTION
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted1 hour ago
We run a high-traffic news and blog platform built with Astro and hosted on Cloudflare, migrated from WordPress. The site publishes 15-20 articles daily with 30-40 images each, totaling 900-1200 images monthly. Currently, the website crashes due to exceeding Cloudflare's daily limits on D1 database reads and Workers KV operations, causing image delivery failures and downtime.
We need an expert to audit and fix database read leaks, optimize the Astro build for edge caching and static site generation, and implement a permanent, cost-effective image storage and hosting architecture. The solution should handle daily publishing and traffic spikes without hitting Cloudflare limits.
Key tasks include fixing D1 query inefficiencies, implementing indexing, rearchitecting page and media delivery with hybrid SSG and edge caching, setting up free scalable image storage using Cloudflare R2, ImageKit, or Cloudinary, and evaluating alternative free hosting stacks like Vercel, Netlify, or Supabase. The project also requires ensuring traffic resilience and providing a live stable deployment.
Deliverables include a detailed audit report, optimized Astro codebase, tested image storage pipeline, architectural comparison of hosting/database alternatives, and a stable live deployment eliminating downtime.
IMP POINTS
1 The site failure is caused by hitting the daily limit of 5000000 rows read on Cloudflare D1 and 100000 operations on Workers KV not because of image storage costs
2 Upgrading to the 5 dollar plan is not required because bad database query design will quickly exceed paid quotas as well
3 Option 1 Keep Cloudflare Pages but convert Astro to 100 percent Static Site Generation SSG so articles compile to pure HTML and trigger 0 database reads during regular visitor traffic
4 Option 2 Connect Cloudflare R2 on its free tier to a dedicated public custom subdomain bypassing Workers and KV entirely to deliver 10 GB of storage and 10000000 free reads per month
5 Option 3 Move image delivery to ImageKit free tier which provides 20 GB of bandwidth and 3 GB of media storage monthly with automatic WebP compression perfectly covering 30 to 40 images per day at 60 to 70 KB each
6 Option 4 Migrate the content architecture away from D1 to Git based Markdown files managed through a free browser editor like Decap CMS removing the need for any database
OR BEST ONE
7 Option 5 Switch hosting to Vercel or Netlify free tiers offering 100 GB of bandwidth and link to a free Supabase database of 500 MB which does not enforce Cloudflare D1 daily row read limits
8 The immediate developer task is to audit Astro configuration change server side rendering to static generation or edge cached routes and stop querying D1 on public page views
We need an expert to audit and fix database read leaks, optimize the Astro build for edge caching and static site generation, and implement a permanent, cost-effective image storage and hosting architecture. The solution should handle daily publishing and traffic spikes without hitting Cloudflare limits.
Key tasks include fixing D1 query inefficiencies, implementing indexing, rearchitecting page and media delivery with hybrid SSG and edge caching, setting up free scalable image storage using Cloudflare R2, ImageKit, or Cloudinary, and evaluating alternative free hosting stacks like Vercel, Netlify, or Supabase. The project also requires ensuring traffic resilience and providing a live stable deployment.
Deliverables include a detailed audit report, optimized Astro codebase, tested image storage pipeline, architectural comparison of hosting/database alternatives, and a stable live deployment eliminating downtime.
IMP POINTS
1 The site failure is caused by hitting the daily limit of 5000000 rows read on Cloudflare D1 and 100000 operations on Workers KV not because of image storage costs
2 Upgrading to the 5 dollar plan is not required because bad database query design will quickly exceed paid quotas as well
3 Option 1 Keep Cloudflare Pages but convert Astro to 100 percent Static Site Generation SSG so articles compile to pure HTML and trigger 0 database reads during regular visitor traffic
4 Option 2 Connect Cloudflare R2 on its free tier to a dedicated public custom subdomain bypassing Workers and KV entirely to deliver 10 GB of storage and 10000000 free reads per month
5 Option 3 Move image delivery to ImageKit free tier which provides 20 GB of bandwidth and 3 GB of media storage monthly with automatic WebP compression perfectly covering 30 to 40 images per day at 60 to 70 KB each
6 Option 4 Migrate the content architecture away from D1 to Git based Markdown files managed through a free browser editor like Decap CMS removing the need for any database
OR BEST ONE
7 Option 5 Switch hosting to Vercel or Netlify free tiers offering 100 GB of bandwidth and link to a free Supabase database of 500 MB which does not enforce Cloudflare D1 daily row read limits
8 The immediate developer task is to audit Astro configuration change server side rendering to static generation or edge cached routes and stop querying D1 on public page views
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.