Website Questions
🤷other
Hi everyone, I’m looking for some guidance on scaling for an upcoming event.
I’m currently on the Supabase Pro plan and building a website that will support an event of roughly 9,000 attendees. The site includes multiple registration forms across different pages, a donation button that redirects to an external giving platform, several videos, and a large number of images.
The frontend is hosted on GoDaddy but might turn to Netlify during testing and Supabase is being used as the backend for handling registrations and storing form data.
My main concern is traffic spikes during registration periods. If several thousand people attempt to register within a short window, I want to make sure the backend won’t become a bottleneck or fail under load.
A few questions:
1. Is the Supabase Pro plan typically sufficient for handling spikes like this if it’s mainly form submissions and database writes?
2. Are there recommended best practices for handling large event registration traffic (rate limiting, queues, edge functions, etc.)?
3. Should I consider any specific database or connection settings to prevent performance issues?
4. Would moving the frontend hosting to something like Netlify or Vercel provide any advantage for handling traffic spikes compared to GoDaddy?
Any advice on architecture or scaling strategies for this type of event site would be greatly appreciated. I want to make sure everything is stable before registrations open.
I’m currently on the Supabase Pro plan and building a website that will support an event of roughly 9,000 attendees. The site includes multiple registration forms across different pages, a donation button that redirects to an external giving platform, several videos, and a large number of images.
The frontend is hosted on GoDaddy but might turn to Netlify during testing and Supabase is being used as the backend for handling registrations and storing form data.
My main concern is traffic spikes during registration periods. If several thousand people attempt to register within a short window, I want to make sure the backend won’t become a bottleneck or fail under load.
A few questions:
1. Is the Supabase Pro plan typically sufficient for handling spikes like this if it’s mainly form submissions and database writes?
2. Are there recommended best practices for handling large event registration traffic (rate limiting, queues, edge functions, etc.)?
3. Should I consider any specific database or connection settings to prevent performance issues?
4. Would moving the frontend hosting to something like Netlify or Vercel provide any advantage for handling traffic spikes compared to GoDaddy?
Any advice on architecture or scaling strategies for this type of event site would be greatly appreciated. I want to make sure everything is stable before registrations open.
