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

171–180 of 374 posts

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

#171

Post by RNCTX »

block_dagger wrote: post #148
kiwicopple wrote: post #136

Earlier quoted context omitted.

You're right about PostgREST. See my comments here: https://news.ycombinator.com/item?id=23321132 > we're supposed to ignore all of the security work that went into making that database software for the past however many decades, and turn it into a dumb storage medium instead I couldn't agree more

With containerization and network orch layer, the db often isn’t the best place to enforce access perms.

I think that's debatable.

A UI without a persistent root/admin connection lingering in the wild cannot leak such a root/admin connection, can it?

How many retail corporations have had breaches resulting in huge credit card dumps that would not have happened if they had not been using frameworks with persistent root/admin database connections outside of their internal office network?

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

#172

Post by Tostino »

sauwan wrote: post #157
bmikaili wrote: post #147

Earlier quoted context omitted.

God forbid someone wants to get money for their product

No one's saying they shouldn't. If the current business model isn't sustainable, then it's a predatory lock-in scheme to monopolize the market and then take advantage of the people who've become dependant on your product.

Couldn't agree more. If major price changes are required to make the product work well after customers have been "enticed" in with a reasonable cost, it is underhanded to say the least.

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

#173

Post by DarkWiiPlayer »

pm90 wrote: post #153
habosa wrote: post #149

Disclaimer: I work on Firebase but I'm always speaking for myself on Hacker News. This looks really cool! Honestly I think the Firebase comparison may be throwing some people off here because this is a SQL-based system, which means there's a huge base of existing tools/techniques/knowledge to build from. I like any tool which makes it easier to build an app. It's 2020 and we still start every app like this: * Pick a…

Maybe I am an old fart, but what’s wrong with the steps you mention? What would your ideal sequence of steps be? If the answer is “just call an api to handle your data” sure that works for POCs/Small apps. But I’m a bit hesitant to put all my businesses data inside a proprietary data store that I don’t control and which isn’t collocated with my app (Ie every data store request makes a round trip to the google server…

What's more, in the days of IaaS you can just as easily spin up a new server in some web interface, copy-paste a setup script you wrote once and after getting a coffee you come back to a working database server that does 90% of what you need. How much automation we use is independent of how much of this automation we decide to outsource.

EDIT: But hey, maybe that's just me not understanding the 2020 mentality of "Take my data and make it work" well enough

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

#174

Post by halfdan »

eatonphil wrote: post #165
pm90 wrote: post #153

Earlier quoted context omitted.

Maybe I am an old fart, but what’s wrong with the steps you mention? What would your ideal sequence of steps be? If the answer is “just call an api to handle your data” sure that works for POCs/Small apps. But I’m a bit hesitant to put all my businesses data inside a proprietary data store that I don’t control and which isn’t collocated with my app (Ie every data store request makes a round trip to the google server…

It's not bad doing it once. Furthermore I'd suggest you do it truly from scratch once just for the learning experience (no framework [Go makes this easy] or from TCP socket [synchronous with Python is easy]). However it's ridiculous going through the same sequence for every single app you build over a career. Nothing changes, it's all just boilerplate. I don't want to ever write this sort of boilerplate code again, I…

Ruby in Rails has this as a feature called "scaffold". https://www.rubyguides.com/2020/03/rails-scaffolding/

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

#175

Post by elitan »

asar wrote: post #90
elitan wrote: post #50

Wow, I thought I created this thread in my sleep. This is exactly what we do at Nhost ( https://nhost.io ) too. I usually explains Nhost as Google Firebase, but: - SQL (PostgreSQL) - GraphQL (Hasura) - 100% open source After being both delighted and frustrated about Firebase I decided that something must be done. The developer experience on Firebase is awesome but the tech and the lock-in effect is super bad. This wa…

I've played around with Hasura and HBP for a side-project and have to say I'm really happy with the developer experience so far. Great work and thanks for making it open source as well!

Happy that you enjoy it. My pleasure.

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

#176

Post by eatonphil »

halfdan wrote: post #174
eatonphil wrote: post #165

Earlier quoted context omitted.

It's not bad doing it once. Furthermore I'd suggest you do it truly from scratch once just for the learning experience (no framework [Go makes this easy] or from TCP socket [synchronous with Python is easy]). However it's ridiculous going through the same sequence for every single app you build over a career. Nothing changes, it's all just boilerplate. I don't want to ever write this sort of boilerplate code again, I…

Ruby in Rails has this as a feature called "scaffold". https://www.rubyguides.com/2020/03/rails-scaffolding/

Rails is probably one of the best ways to not waste time. I knew they had some of this capability but I wasn't sure if they generated the whole controller, fully hooked up to the models, too.

The only thing that turns me off about Rails and .NET is that it's a big learning curve _because_ the projects are so feature complete. Since I haven't worked professionally in either of them, I haven't been able to get myself to learn either well enough to do rapid prototyping.

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

#178

Post by electriclove »

rhlsthrm wrote: post #134
BiteCode_dev wrote: post #97

A bit of a plug, but if you wish for something that has the Postgres reliability, the taste of nosql but with strong typing and a json output a la graphql, give a try to edge db: https://edgedb.com The team behind it is awesome (one is a python core dev), and it's a FOSS, but they have been using it internally for some time.

I feel like this is close to what I'm looking for but not quite there in terms of minimal boilerplate backend. Basically what I want to do is write a GraphQL schema and have that be the ultimate source of truth. The schema then should generate the full DB (honestly I don't even care if it's SQL, NoSQL, etc. the idea is that part is abstracted away). Then the schema can generate fully typesafe queries for the front en…

https://dgraph.io/blog/post/dgraph-graphql-hits-ga/

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

#179

Post by RNCTX »

pm90 wrote: post #155
RNCTX wrote: post #129

I see from the links that this is probably borrowing a bit from Postgrest? I've just discovered Postgrest in the past few days and along with Postgraphile it seems like all of these projects aimed at "getting back to the database" are a good idea, I like it. It always bothered me that the first order of business with any software development framework was to provide a root/admin database connection. It's like, this t…

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…

Not every database application is a public facing web application.

Think about, for instance, a company's internal customer database (including billing, etc), accessed with internal tools. CSR/Support people need to be able to see billing status but not credit card numbers, for example. Different levels of management need to be able to generate reports, but again not get credit card numbers.

For these use cases the opposite is true. The further you take auth and permissions away from the database/devops admins, the more times you're going to need to reinvent auth and permissions boilerplate for every internal tool under the sun.

Which is a pointless exercise if none of the tools in question are ever going to be accessible outside of the company's VPN anyway.

Active Directory / LDAP are not abandoned technologies, after all.

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

#180

Post by kiwicopple »

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…

> My bet is that you can generate an entire API _and_ basic CRUD browser UI from a db schema

That's what we're building! We already have the auto-APIs, and auto-documentation. The auto-UI is in the works. It essentially is Airtable, but backed by Postgres

Also, we will provide "meta" REST APIs for your database. Want to programmatically add columns or fetch all your database types? No probs.

Post reply on HN