4 ms·
It’s worth mentioning that portability is one of our core Principles at Supabase too: https://supabase.com/docs/guides/getting-started/architecture#everything-
by kiwicopple 3y ago
It’s worth mentioning that portability is one of our core Principles at Supabase too:
https://supabase.com/docs/guides/getting-started/architecture#everything-is-portable https://supabase.com/docs/guides/getting-started/architectur...
This is why we don’t run a fork of Postgres, and we lean heavily into extensions rather than customizations. As the docs mention: this forces us compete on experience.
(Speaking here to your point about supabase, not to detract from Nile, which looks very cool)
- endigma 3y agoI use Supabase at work for this reason, just not sure I'm _completely_ prepared to pick up and move to a non-Supabase PG if I really had to, which is a little unsettling for long term reliability. This is probably a me problem, you guys are doing great work on avoiding lock-in.
- kiwicopple 3y agoI recommend complimenting the supabase tooling with “external” tooling - pgadmin, direct Postgres libs, etc. Even if you don’t migrate (which we hope you never do) you’ll definitely become more seasoned Postgres developer and you should find that we’re not doing anything too “magical”. Everything you learn with supabase should be transferable
- infra_dev 3y agoHey kiwicopple, big virtual hi. I am a fan of your work.
- kiwicopple 3y agocongrats on the launch!