|
|
|
|
|
by adamcharnock
209 days ago
|
|
In this particular case the only need was for Postgres migration, no other services needed. The problems we've seen or heard about with Supabase are: * Cost (in either magnitude or variability). Either from usage, or having to go onto their Enterprise-tier pricing for one reason or another
* The usual intractable cloud-oddities – dropped connections, performance speed-bumps
* Increased network latency (just the way it goes when data has to cross a network fabric. Its fast, but not as fast as your own private network)
* Scaling events tend not to be as smooth as one would hope None of these are unique to Supabase though, they can simply all arise naturally from building infrastructure on a cloud platform. Regarding self-hosted Supabase - we're certainly open to deploying this for our clients, we've been experimenting with it internally. Happy to chat with you or anyone who's interested. Email is adam@ company domain. |
|