Migrating from Supabase
hey hn, supabase ceo here<p>the Val Town team were kind enough to share this article with me before they released it. Perhaps you know from previous HN threads that we take customer feedback very seriously. Hearing feedback like this is hard. Clearly the team at Val Town wanted Supabase to be great and we didn’t meet their expectations. For me personally, that hurts. A few quick comments<p>1. Modifying the database in production: I’ve published a doc on Maturity Models[0]. Hopefully this makes it clear that developers should be using Migrations once their project is live (not using the Dashboard to modify their database live). It also highlights the options for managing dev/local environments. This is just a start. We’re building Preview Databases into the native workflow so that developers don’t need to think about this.<p>2. Designing for Supabase: Our goal is to make all of Postgres easy, not obligatory. I’ve added a paragraph[1] in the first page in our Docs highlighting that it’s not always a good idea to go all-in on Postgres. We’ll add examples to our docs with “traditional” approaches like Node + Supabase, Rails + Supabase, etc. There are a lot of companies using this approach already, but our docs are overly focused on “the Supabase way” of doing things. There shouldn’t be a reason to switch from Supabase to any other Postgres provider if you want “plain Postgres”.<p>3. That said, we also want to continue making “all of Postgres” easy to use. We’re committed to building an amazing CLI experience. Like any tech, we’re going to need a few iterations. W’re building tooling for debugging and observability. We have index advisors coming[2]. We recently added Open Telemetry to Logflare[3] and added logging for local development[4]. We’re making platform usage incredibly clear[5]. We aim to make your database indestructible - we care about resilience as much as experience and we’ll make sure we highlight that in future product announcements.<p>I’ll finish with something that I think we did well: migrating away from Supabase was easy for Val Town, because it’s just Postgres. This is one of our core principles, “everything is portable” (<a href="https://supabase.com/docs/guides/getting-started/architecture#everything-is-portable">https://supabase.com/docs/guides/getting-started/architectur...</a>). Portability forces us compete on experience. We aim to be the best Postgres hosting service in the world, and we’ll continue to focus on that goal even if we’re not there yet.<p>[0] Maturity models: <a href="https://supabase.com/docs/guides/platform/maturity-model">https://supabase.com/docs/guides/platform/maturity-model</a><p>[1] Choose your comfort level: <a href="https://supabase.com/docs/guides/getting-started/architecture#choose-your-comfort-level">https://supabase.com/docs/guides/getting-started/architectur...</a><p>[2] Index advisor: <a href="https://database.dev/olirice/index_advisor" rel="nofollow">https://database.dev/olirice/index_advisor</a><p>[3] Open Telemetry: <a href="https://github.com/Logflare/logflare/pull/1466">https://github.com/Logflare/logflare/pull/1466</a><p>[4] Local logging: <a href="https://supabase.com/blog/supabase-logs-self-hosted">https://supabase.com/blog/supabase-logs-self-hosted</a><p>[5] Usage: <a href="https://twitter.com/kiwicopple/status/1658683758718124032?s=20" rel="nofollow">https://twitter.com/kiwicopple/status/1658683758718124032?s=...</a>