3 ms·
This isn't fair feedback. You have to be more specific about the "lock in". Supabase itself is just managed Postgres and can be self-hosted. The entire point is
by Difwif 2y ago
This isn't fair feedback. You have to be more specific about the "lock in". Supabase itself is just managed Postgres and can be self-hosted. The entire point is that everything they offer is open source and easily found elsewhere.
I can imagine they fall short in some aspects from that ideal and I would love to know your experience but even with your first sentence this is just a pretty damning write off.
Disclaimer: I'm NOT a Supabase employee, just a happy user.
- BoorishBears 2y agoPeople keep writing this, doesn't Supabase rely on spinning up additional services to leave, meaning you can't leave to another managed offering? Off the top of my mind, PostgREST and go-true? https://github.com/supabase/auth https://github.com/supabase/auth - If you use Postgres you're "locked" into Postgres: a technology with a laundry list of providers. If you leave Supabase, you'll lose the fully managed aspect of 99% of the Postgres providers out there, which confirms the pain the parent comment is describing.
- xytofs 2y agoYou can just take the Auth server, run it yourself with an AWS RDS instance for example, keep up with updates and be good to go. Yes you get a good UI with Supabase, and even much of that can be hosted yourself.
- kiwicopple 2y agothis is no different than running, say, Rails on a managed service. You can take the service and you run it somewhere else: each individual service is wrapped into a docker image which should make it easy. You can use as many or as few of the services as you want - its designed it that way: https://supabase.com/docs/guides/getting-started/architecture#everything-works-in-isolation https://supabase.com/docs/guides/getting-started/architectur...
- BoorishBears 2y agoThis just sidesteps what I said? Supabase is most attractive to those without the skills to run an unmanaged service A bespoke solution, even if it's open, doesn't mean it's as portable as a very standard solution. If you want portability, the parent comment was right: don't embed Supabase deeply into your application.
- kiwicopple 2y agolet me have another run at it: > If you use Postgres you're "locked" into Postgres: a technology with a laundry list of providers. Supabase is just a Postgres platform, and you can use it like that so that you can migrate away to any one of those laundry list. We _also_ provide some tools which are nicely integrated but importantly: they are optional > doesn't Supabase rely on spinning up additional services to leave, No, not if you don't use those other services. If you _do_ decide to use another service, then yes, you need to spin it up to leave (or migrate to something else). Hence my comment: this is no different than running, say, Rails on a managed service.
- switchbak 2y agoYou're suggesting a hosted Postgres offering isn't "as portable" as a very standard solution? This isn't DynamoDB here, this is about as standard as it gets. I'm failing to find the supposed lock-in being talked about here.
- BoorishBears 2y ago