The conversation

Lessons learnedExperience excerpt · English

- We started out using their hosted product for both our DB, storage, auth, and functions

… - 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 so we decided to move to our own API servers: https://github.com/supabase/edge-runtime/issues/212 - Now, the connection between our API servers and the database was slow (a few hundred ms per query), so we moved to self-hosting Postgres which was pretty painful. We tried to use https://github.com/supabase/postgres , but the documentation was very lacking and we had to make a bunch of modifications to get it to work. After we got it working, it was pretty smooth though - pretty easy to implement backups, etc. - Our latest issue has been around auth where the cookie name options change. We've spent hours debugging random cookie issues deep in the auth framework (they finally released `@supabase/ssr` which is pretty decent, but we're still thinking about moving to handling auth on our side so we know and can debug the logic). …

Original discussionWe are moving to General Availability100 source comments · at import
2

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

KI

> 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

Full original
K_

Tried Supabase but currently only use their Auth. The server to database latency was very high(few hundred ms) whereas Planetscale DB in the same region gives sub 10ms. Still great option for most projects that can do with these issues.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.