www.youtube.com
Why I won't use supabase (but you might)
Excerpt
Discover why Supabase might not be the best choice for your backend needs, but could still be perfect for certain projects. In this video, I dive into my personal experience building a school club catalog app with Supabase and React. I'll explore the challenges I faced with Supabase's developer experience, database management, row-level security, and edge functions. … {ts:55} but forget about collaborating or working with anyone in the future migrating and version controlling your {ts:59} dat datase is an absolute nightmare there are no guides to structured development with super base so most of {ts:65} the time you just have to wing it what I had to do was I had to create a master GitHub repo of all my SQL commands which {ts:71} was just a pain to manage and write docs on another feature I had a problem with was Ro level security which is just {ts:77} configuring permissions for your SQL table for example you might have a policy where only site admins can make {ts:83} API requests that manage user data in small projects it's great because you don't need to worry about backend … {ts:106} route to take care of other functionality such as emailing the user and more complicated meeting validation {ts:111} logic so now you have to split up your backend into R level security and Edge functions which makes it difficult to {ts:116} keep track of back in logic to top that off super vase Ed functions use the Deno runtime instead of nodejs this was a {ts:123} problem for me because I ran into compatibility issues with my npm libraries for example you can't use {ts:128} Google apis of Deno and for other libraries you have to find Deno equivalents or else your app crashes in {ts:133} production honestly Edge functions weren't that bad but I find myself needing them a lot and at that point I … {ts:173} with not much Deno support for existing libraries incompatibility with npm packages and very little Community {ts:179} Support when it comes to self-hosting I have to spend hours finding workarounds myself so if you're thinking about {ts:184} self-hosting super base it isn't easy the only convenient solution is to pay into one of their subscriptions I'll be {ts:190} honest subase isn't the worst solution for serious projects I would just use it as a free database connected to an omm {ts:197} but I would skip out on the backend as a service part of it there's just too many limitations where it really shines {ts:202} though is small projects and hackathons if you're sure that you're not going to work on your app for more than 3 months
Related Pain Points
Ecosystem fragmentation across package managers and runtimes
6Developers must maintain package compatibility across multiple package managers (npm, pnpm, yarn) and JavaScript runtimes (Node, Deno, Bun), significantly complicating maintenance and distracting from security concerns.
No structured development guidelines for database version control
6Supabase lacks guides for structured database development. Developers must create workarounds like master GitHub repos of SQL commands and custom documentation, making collaboration and migration difficult.
Row-Level Security policies difficult to debug and manage
6Debugging RLS policies requires diving into the Supabase dashboard, making them disconnected from the main codebase. Complex policies are time-consuming to debug and misconfiguration can expose data.
Ecosystem Immaturity and Limited Third-Party Integrations
5Supabase's ecosystem is still immature with limited third-party integrations and fewer community resources compared to Firebase. Solving edge cases often requires digging through GitHub issues instead of finding documented solutions.