21–30 of 82 posts
Earlier quoted context omitted.
That is the exact solution we went with :)
So then why mention that FB is gated? It isn't gated, the design of your application was off.
Earlier quoted context omitted.
So then why mention that FB is gated? It isn't gated, the design of your application was off.
it is gated. 60 endpoints in a minute. thanks to OP i now know this.
First thing I always do is read the quotas/limits on any google cloud product before I use it.
Then, I'd notice the increase in deployment times on my CI server as more functions were being added and inspect what was taking so long and try to optimize it. Those individual endpoints take a while to deploy...
Earlier quoted context omitted.
So then why mention that FB is gated? It isn't gated, the design of your application was off.
This is obviously a (hacky) work-around. Firebase Functions are designed to be deployed individually- abandoning that costs you GCP log traces and boilerplate right off the bat. Read the Firebase Functions documentation, and you'll see no mention of designing your application this way.
Once you get past a certain amount of endpoints, I'd always want to declare my endpoints in code rather than be tied to their config.
Never had an issue with the logs. Requests still show up.
I'm going to have to very kindly ask the Supabase devs to stop making such an appealing development platform as I don't have the time/energy to rewrite my existing web/apps. But for real, congrats on this and it looks very nice. At this point I'm just waiting on a new project that would be a good fit so I can play with all of this. Keep up the great work!
v2 isn't a huge change from v1, if you have anything existing that you need to migrate. The Typescript support should be quick/easy (if you used it in v1, it's mostly removing from a bunch of your methods). A lot of this is preparing for mutliplayer functionality (coming on thursday) - we needed a breaking change to support Phoenix's presence/broadcast interface.
I love the concept of Supabase. The Firebase model is powerful but gated. For example, I recently had a project exceed FB's quota of functions- you can't deploy more than 60 endpoints in a minute which is a nightmare for CI pipelines which redeploy the entire app [0]. We recently tried Supabase on a "frontier" project, and found that it wasn't quite mature enough for production use in our case. Intermittent network e…
> Intermittent network errors
I'm curious about where you're seeing these errors - is this your database functions or "Edge Functions" (Deno)?
I'm going to have to very kindly ask the Supabase devs to stop making such an appealing development platform as I don't have the time/energy to rewrite my existing web/apps. But for real, congrats on this and it looks very nice. At this point I'm just waiting on a new project that would be a good fit so I can play with all of this. Keep up the great work!
I think the best part is that if you're willing to go all in on RLS for your authorization, you can do away with needing a backend for your typical crud operations and use their functions for things like webhooks, or the occasional endpoint for more complicated operations.
I find myself saying this a lot when I try and explain the concept of Supabase. We don't really emphasize this very much on our website either.
Disclaimer: I work at Supabase.
Has any used Fly.io app hosting with Supabase-JS for the DB? I'm curious to hear people's experience.
It worked great. That's just the database part - from there you'll need to deploy the middleware too
Earlier quoted context omitted.
its brought up every time supa is on hn. reasonable qtn but here you go https://news.ycombinator.com/item?id=32440018
Your answer didn't answer anything and was a bit terse. Their question was valid. It looks like the answer is that they're charging some sort of licensing fee per project using Supabase or that they have a hosted option for people who don't want to run their own Supabase instance(s): https://supabase.com/pricing .
Supabase is very liberally licensed (MIT, Apache2, PostgreSQL, depending on the tool), and we don't plan to pursue any revenue from licensing. We make enough money from database hosting.
hope that clears things up a bit
Maybe it's been discussed before but since it's a VC backed company, what's their business model? They raised a ton of money. How do they plan on getting that back?
we have a hosted platform - you can sign up and spin up a postgres database, and we charge you $25/month (+ additional usage over a certain quota).
This model is proving to be fine for us. It's very common for developers to pay for a database, especially a full Postgres database (more-so than say, a frontend hosting solution). We have a free tier too, where we pause the database if it is unused for a week. This good for the planet, and our bottom-line
Supabase user here. Ive been happy with Supabase. It feels like the recent launches have been underwhelming. I am really pumped for Neon and think they are doing something more differentiated.