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

Supabase (YC S20) – An open source Firebase alternative

supabase.io

Post reply on HN
Print view View original

341–350 of 374 posts

Re: Supabase (YC S20) – An open source Firebase alternative

#341

Post by mav3rick »

sparkie wrote: post #334
mav3rick wrote: post #331

Earlier quoted context omitted.

This is literally what Apple does and HN goes gaga over it. Literally only first party core services are allowed and given special privileges.

Yeah, I wouldn't touch an Apple product either. I get your point that people expect differently from Google, but Google brought that upon themselves by marketing Android as an open source alternative to iOS. Now they've got the market share and developers, they're no longer interested in marketing it this way and are now apparently more interested in cementing the walled garden. The battery issue is a valid concern,…

And Android is open source. I'm sure you can Google the URL. The same can't be said about Apple. Do you see the iOS source anywhere ?

Re: Supabase (YC S20) – An open source Firebase alternative

#342

Post by _lbaq »

Zenst wrote: post #273
_lbaq wrote: post #140

There is a database management company called Superbase, the names are confusingly similar. I read a bit perplexed about Superbase being a YC company. https://www.superbase.com

Superbase IIRC was a GEM based database system that was the era of windows 1.0 comming to birth. Was nice, I mostly did work in Dataease then, and talking late 80's era. Dig into the history shows more in depth from my GEM flavour experience. https://en.wikipedia.org/wiki/Superbase_(database)

https://www.superbase.com/products/superbase-ng-professional...

Re: Supabase (YC S20) – An open source Firebase alternative

#344

Post by mav3rick »

hilbertseries wrote: post #320
bawana wrote: post #203

Earlier quoted context omitted.

The pseudo-democratic silicon valley model of freemium is the problem. Seducing you into using something with the word 'free' but then trapping you with a changing API and cost structure. They should be up front with the realization that our ability to pay THEM is not commensurate with use by OUR users. Fees should based on OUR revenue, not usage.

> Fees should based on OUR revenue, not usage. So if someone builds a business that makes very little money but uses a ton of compute, the cloud provider should subsidize that? And conversely if you make a ton of money using barely any compute, you should pay your cloud provider a premium? This business model makes no sense.

Seen a lot of non sense but the op's model is right up there.

Re: Supabase (YC S20) – An open source Firebase alternative

#345

Post by Zenst »

_lbaq wrote: post #342
Zenst wrote: post #273

Earlier quoted context omitted.

Superbase IIRC was a GEM based database system that was the era of windows 1.0 comming to birth. Was nice, I mostly did work in Dataease then, and talking late 80's era. Dig into the history shows more in depth from my GEM flavour experience. https://en.wikipedia.org/wiki/Superbase_(database)

https://www.superbase.com/products/superbase-ng-professional...

Yes, still going and interestingly enough, so is dataease. Though the old secret dos debug system in dataease is probably long gone (hold down ctrl and type debug and you'd get hidden developer options). Software today tends not to have as many hidden gems like that as yesteryear, bugs perhaps but hidden features, less so.

Re: Supabase (YC S20) – An open source Firebase alternative

#346

Post by kiwicopple »

fulafel wrote: post #337
kiwicopple wrote: post #79

Earlier quoted context omitted.

See my comments on Auth here: https://news.ycombinator.com/item?id=23320443 > We want to nail the auth and we're looking at leveraging Postgres' native Row Level Security. This is a tricky task to "generalize" for all businesses but we have some good ideas (we're discussing in our repo if you want to follow - https://github.com/supabase/supabase ) > RESTful APIs I can of course get with PostgREST That's what we use!…

Are you also using PostgREST in the backend to provide the APIs, or are your REST APIs and hence client libs PostgREST compatible?

Each database gets it's own PostgREST instance, a realtime server, an API proxy, and a Postgres admin api (which we are building) to manage their schema programatically.

We have client libraries for PostgREST, which then gets installed as a dependency in our main client library.

Re: Supabase (YC S20) – An open source Firebase alternative

#347

Post by kiwicopple »

gavinray wrote: post #311
kiwicopple wrote: post #18

Earlier quoted context omitted.

Good question - one we get asked often. We don't use GraphQL (but you can do deep-queries: https://supabase.io/docs/library/get#query-foreign-tables ) Under the hood we use PostgREST. At the same time, we may (also) offer GraphQL using Postgraphile, so people can bring their own client-library. Differences from Hasura: - Auth: we will use Postgres RLS - Realtime: we don't use triggers, we use WAL (much more scalable)…

Are you serious? Two of your points are future feature promises . One of them is how Hasura plans to support other DB's besides Postgres, which they've already been exclusively working on & supporting for multiple years at this point. Another mentions that you have plans to build a UI for non-technical people. This isn't different either, Hasura already has this too. The triggers part is also downright wrong. Check t…

You're 100% correct about their triggers and thanks for the link. I actually hadn't read it but I did today after waking up and it's quite fascinating.

Hasura is a great product and it deserves all the love it gets here. Tanmai and exchanged a few messages in February, so we're aware of what eachother are working on. I don't really feel this space is a player-takes-all market (see also nhost, graphile, subzero, amplify - all great products).

The parent comment "how is it going to compare" so I listed a couple of promises. It's up to us now to deliver on those promises - we're only a small team and our startup is 5 months old, but we move fast. I don't plan to disappoint. Sorry this reply took a few hours, I wanted to make sure I read your link (and slept) before commenting.

Re: Supabase (YC S20) – An open source Firebase alternative

#348

Post by neop1x »

bavell wrote: post #181
pm90 wrote: post #155

Earlier quoted context omitted.

I may be wrong about the history of security work on databases (feel free to correct me!) , but I think the security model was built mostly for an age where a single DB would be used by many apps, thus access control at the DB level seemed natural to the DB admins. Today, with managed/containerized DBs and Microservices and share nothing architecture, I’ve seen most apps use their own database instance, in which case…

I'm curious to hear what others think about this as well. I run some WordPress sites in containers and I give each one it's own DB instance. I just create the root account with a strong password, give it to WordPress and call it a day. Makes ops much simpler although it's probably not the best use of resources (e.g. memory). Any big downsides to doing things this way? I'm no DBA so I appreciate any insights.

Scaling, durability and backup. Your single small container DB may not be able to serve high requests per second. It depends on the architecture and caching, though. If it goes down, your app goes down, no failover or replicas. And it is difficult to backup many isolated DB instances.

Re: Supabase (YC S20) – An open source Firebase alternative

#350

Post by eatonphil »

eatonphil wrote: post #159

This is really interesting. I spent a while a few weeks ago looking around for a serious, open-source BaaS effort backed by... anyone. I've been influenced by code generators like xo/xo [0] and sqlboiler [1] recently (so you can have type-safe APIs and you still manage/own the resulting code). My bet is that you can generate an entire API _and_ basic CRUD browser UI from a db schema. I've been working on a code gener…

Here's [0] the docs site for the code generator I'm working on. It generates a Go REST API with basic CRUD operations (plus filtering, pagination and sorting).

Next up is authentication and a React UI.

[0] https://eatonphil.github.io/dbcore/

Post reply on HN