Hey folks,
I've been running into accessibility issues with Supabase from various networks in India. My web app heavily relies on Supabase for a PostgreSQL database, user authentication, file storage, and real-time features. Since my entire backend is tied to Supabase, I'm exploring migration options.
I'm considering two paths:
1. Using Neon for PostgreSQL, Clerk for authentication, Cloudinary for file storage, and Pusher for real-time functionality.
2. Moving to Firebase, though I'm concerned about my PostgreSQL-based database schema.
I'd love to know which of these options would be easier and offer more long-term flexibility. Is splitting services better than going fully with Firebase? Any advice would be greatly appreciated!
4 Answers
Here's a hot take: Instead of depending on third-party services, why not build your own application logic and manage it yourself? That way, you have full control over everything. It's wild that Supabase is down—do you know if this is a temporary routing problem or a bigger issue with geo-blocking?
Have you thought about self-hosting Supabase on a VPS like DigitalOcean or Hetzner in major cities around India? That way, you can maintain your Postgres schema, authentication, and storage without having to deal with any migration hassle. It might actually be quicker than reworking everything for Neon and Clerk.
Following this conversation closely. It’s been a tricky situation!
I’d suggest looking into GCP or AWS for your transition; they can provide good alternatives that might suit your needs better.
I hadn't thought of that, but now that Supabase seems to have resolved their issues, it might not be necessary anymore!