Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We are moving to General Availability

supabase.com

Post reply on HN
Print view View original

31–40 of 106 posts

Re: We are moving to General Availability

#31

Post by xytofs »

BoorishBears wrote: post #30
Difwif wrote: post #27

Earlier quoted context omitted.

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:…

People 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 - 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 o…

You 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.

Re: We are moving to General Availability

#32

Post by stemc43 »

trolan wrote: post #6
kelsey98765431 wrote: post #4

This is not a negative statement against Supabase, but heed my warning: Do not build out your MVP on supabase. If you need to scale and want a MSP do it after the MVP. Detangling the lock in is not fun. Everything offered by supabase is easily found elsewhere without the MSP lock in.

I've used it for a couple uni/personal projects to get some experience, and firebase for the same. I'm concerned about getting locked in, what other providers do you recommend who can let me migrate more easily?

supabase, directus and similar are just wrappers on top op postgres. I just spin up local postgres instance for personal project and see no reason to get vendor locked-in myself.

Re: We are moving to General Availability

#33

Post by benzible »

lbrito wrote: post #19

Any news on the integration with Fly.io going GA?

From a recent post by a fly.io employee in their forums [1], in response to being asked "do you expect it to be ready for production use this year?"...

>Coming very soon, we’ll be moving to public alpha (which in our world, comes after private beta :smiley:).

[1] https://community.fly.io/t/supabase-managed-postgres-in-priv...

Re: We are moving to General Availability

#34

Post by trevoragilbert »

Happy Supabase user here, albeit on a tiny app I work on in my spare time. So no comment for larger or more complex orgs.

That being said, the Swift documentation could use some love. It’s not terrible but it’s also not great. There have been a number of times when I wanted to do something, ended up reading about it on the Supabase JS documentation, and then thought “well I assume it’s roughly the same in the Swift library.” It worked, but a pain to have to guess a lot.

Re: We are moving to General Availability

#35

Post by SadWebDeveloper »

I'm a full stack developer and still don't know what supabase does other than being a firebase replacement...

Like seriously are they seriously trying to sell us how difficult is to setup a simple nginx server? Not sarcastic just an old developer that hasn't get this new fad of going "serverless".

Re: We are moving to General Availability

#36

Post by kiwicopple »

trevoragilbert wrote: post #34

Happy Supabase user here, albeit on a tiny app I work on in my spare time. So no comment for larger or more complex orgs. That being said, the Swift documentation could use some love. It’s not terrible but it’s also not great. There have been a number of times when I wanted to do something, ended up reading about it on the Supabase JS documentation, and then thought “well I assume it’s roughly the same in the Swift l…

we just took over official support for swift: https://supabase.com/blog/supabase-swift

I'll let Guilherme know. feel free to reach out directly with any specific feedback

Re: We are moving to General Availability

#37

Post by listenallyall »

atonse wrote: post #14
kelsey98765431 wrote: post #4

This is not a negative statement against Supabase, but heed my warning: Do not build out your MVP on supabase. If you need to scale and want a MSP do it after the MVP. Detangling the lock in is not fun. Everything offered by supabase is easily found elsewhere without the MSP lock in.

We're using Supabase for a client project and even three sprints in, we're severely hobbled by having to play with a couple of architectural choices forced on us with Supabase and Supabase Auth. Any of the time savings benefits have been wiped out already just fighting the choices and also the subtle differences between the local dev environment, implementing RLS without good tooling. On an architectural level, it is…

Kinda sounds like "client side connections to postgres" was the poor decision at root of your security concerns, not the choice of provider

Re: We are moving to General Availability

#38

Post by giraffe_lady »

SadWebDeveloper wrote: post #35

I'm a full stack developer and still don't know what supabase does other than being a firebase replacement... Like seriously are they seriously trying to sell us how difficult is to setup a simple nginx server? Not sarcastic just an old developer that hasn't get this new fad of going "serverless".

It's not serverless it's a postgrest API over a DB. Which is plenty of backend for many of my purposes. Postgres's RBAC is sophisticated enough to use as your entire auth layer if you know what you're doing with it. After that it's a free rest API.

I'm not like a supabase diehard or whatever but I have used it to great success in a handful of projects, especially early or proof-of-concept stage ones. For me it's not a replacement for nginx it's a replacement for rails.

Re: We are moving to General Availability

#39

Post by kiwicopple »

jmeyer2k wrote: post #22

Congrats on the launch! Here's our experience with Supabase at https://automark.io (Next.js + Supabase). - First of all, Supabase let us launch fast which was amazing. Super powerful Postgres features without the pain of self-hosting (or so we thought). - We started out using their hosted product for both our DB, storage, auth, and functions. - Functions have a critical bug that prevent us from using in development s…

> We're pretty satisfied with Supabase as an open source project

As an open source company, we'll take that as a mark of success.

Thanks for the details, I'll jump into that GH issue with the Edge Functions team after this week

Re: We are moving to General Availability

#40

Post by srcreigh »

listenallyall wrote: post #37
atonse wrote: post #14

Earlier quoted context omitted.

We're using Supabase for a client project and even three sprints in, we're severely hobbled by having to play with a couple of architectural choices forced on us with Supabase and Supabase Auth. Any of the time savings benefits have been wiped out already just fighting the choices and also the subtle differences between the local dev environment, implementing RLS without good tooling. On an architectural level, it is…

Kinda sounds like "client side connections to postgres" was the poor decision at root of your security concerns, not the choice of provider

Client side connections and RLS are the Supabase blessed path in the getting started docs
Post reply on HN