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

Supabase (YC S20) raises $80M Series B

techcrunch.com

Post reply on HN
Print view View original

51–60 of 130 posts

Re: Supabase (YC S20) raises $80M Series B

#51

Post by robertlagrant »

searchableguy wrote: post #17
_query wrote: post #13

Earlier quoted context omitted.

It's using Postgres pg_notify to subscribe to tables and using a WebSocket server to distribute the changes. The table watcher is written in Haskell and based on the IHP haskell framework. Using Haskell makes it very easy and efficient to deal with lot's of active sessions in parallel. You can find the source code here https://github.com/digitallyinduced/ihp/blob/master/IHP/Data... if you're interested :)

That's a similar approach to supabase. Why reinvent the wheel? (I'm asking out of curiosity here). Why websockets? Do you allow bidirectional communication? If not, wouldn't it be better to use http push for easier scaling?

> That's a similar approach to supabase. Why reinvent the wheel?

Supabase is a copy of Firebase. Same question?

Re: Supabase (YC S20) raises $80M Series B

#53

Post by ehathaway »

sk55 wrote: post #11

For people who have some experience in this, what's the best less-code backends? Hasura? Supabase? Prisma? Thin?

I don't think there is a "best".

I think Firebase has the lowest barrier to entry and if you don't exceed the pricing tiers, its a very pleasant experience.

Hasura and Prisma are both awesome, but after having worked in GraphQL a lot, I now try to stay at least 10 feet away at all times from GraphQL paradigms unless their hidden costs can be justified for the project.

I haven't used Thin, but it looks like its React only. If there was a Svelte or JS agnostic option Id give it a try.

Re: Supabase (YC S20) raises $80M Series B

#54

Post by michelpp »

babl-yc wrote: post #14

My main critique after trying Google Firestore was: (1) Lack of typed schemas with declarative definitions (2) Read/write permissions and write validation was extremely complex From quick glance at the docs, it looks like they make progress towards the first but not sure about the latter: https://supabase.com/docs/guides/auth/row-level-security

Disclaimer: I work at Supabase on database security.

The link you posted is a great guide to sensible security practices with Supabase. It's worth noting that the feature highlighted, Row Level Security (RLS) is a native Postgres feature and not Supabase specific in any way.

https://www.postgresql.org/docs/current/ddl-rowsecurity.html

One immediate benefit of using native security is that it applies to all types of database clients and tools uniformly. we're not blocked in the future adding more integrations. And it works both ways, if you are using RLS in an existing postgres deployment you can migrate to Supabase and your existing trusted policies will come with you.

It also means that we can avoid creating a whole class of security bugs by starting from scratch, and take advantage of the millions of collected human-hours of work that already exists. Security is hard because it is adversarial and it is hard to reproduce or even conceptualize a truly threatening environment without experience.

One of our guiding principals is to stand on the shoulders of the core developers and not implement our own core security model, but to use the native one as a foundation for even more powerful security concepts to come. We're actively discussing a lot of ways to make this even easier and safer for customers.

Re: Supabase (YC S20) raises $80M Series B

#56

Post by hawthornio »

kiwicopple wrote: post #41

supabase ceo here. I want to give a big shout-out to the HN crowd. You have been instrumental in our growth - both from a traction perspective, but even more so for product development. From our initial launch 2 years ago[0], where everyone told us we need auth, to our Auth[1], Storage[2], Functions[3], and GraphQL[4] launches. You are always giving great (and usually tough!) feedback which helps guide the team and p…

Seems like there’s a typo in Pricing FAQ (emphasis mine):

> Additional usage costs are billing are also billed at the end of the month.

Re: Supabase (YC S20) raises $80M Series B

#57

Post by _query »

jonotime wrote: post #47
sk55 wrote: post #11

For people who have some experience in this, what's the best less-code backends? Hasura? Supabase? Prisma? Thin?

I like Hasura personally and use it on personal projects. Thin looks awesome but I cant tell if there is a way to self host.

Thin self-hosting is coming soon :) We already have this working on the technical side, we just need to add more documentation before we can push it out.

Re: Supabase (YC S20) raises $80M Series B

#58

Post by _query »

ehathaway wrote: post #53
sk55 wrote: post #11

For people who have some experience in this, what's the best less-code backends? Hasura? Supabase? Prisma? Thin?

I don't think there is a "best". I think Firebase has the lowest barrier to entry and if you don't exceed the pricing tiers, its a very pleasant experience. Hasura and Prisma are both awesome, but after having worked in GraphQL a lot, I now try to stay at least 10 feet away at all times from GraphQL paradigms unless their hidden costs can be justified for the project. I haven't used Thin, but it looks like its React…

Thin also supports other JS frameworks. Svelte docs can be found here https://thin.dev/docs/svelte We're focussing the communication on react mostly to keep things simple. The core of thin is independent of react.

Re: Supabase (YC S20) raises $80M Series B

#59

Post by tough »

chrisweekly wrote: post #20
sk55 wrote: post #11

For people who have some experience in this, what's the best less-code backends? Hasura? Supabase? Prisma? Thin?

Please remedy my ignorance if I might be wrong, but I thought Prisma was an ORM, not a true backend.

Yes, you can use both supabase and prisma with your own postgres database

https://supabase.com/docs/guides/integrations/prisma

Re: Supabase (YC S20) raises $80M Series B

#60

Post by MaxLeiter »

I just started using Supabase on a small side project and am very impressed; the ease of setting up realtime was amazing. However, the dashboard is so slow. Every action that has a server request results in a spinner, even if it could be instant, like creating an empty unnamed sql query.
Post reply on HN