Hacker News Reader

Comment by trailbase | Hacker News Reader

IIUC, what you're asking for is what it is, i.e. TrailBase is like FireBase, as opposed to a FireBase running entirely on the client. We probably both agree that ACLs enforced by the client are no protection at all.

Did I misunderstand? Was there something that thew you off? - always keen to improve

View on HN

No I meant, is it "just like Firebase (ACLs on the backend) but simpler"?

I understand ACLs on the backend and API queries on the client, I just don't find it that practical to use

Could you expand a bit on, how

> I feel I prefer to have a locked-down database, and implement everything "backend-side" with a kind of "admin API" which has access to everything, and checks user roles in the backend, it feels cleaner to me, is that also possible?

is different from what FireBase or TrailBase does?

Are you saying that you'd prefer to run your own backend binary (as opposed to running in an integrated runtime), do your own ACL checking, and have more of a free-form SQL-like API with the DB layer?

Yes, I prefer to have no direct access to the database from the client, just go through my API, and my API handles ACLs and do the SQL calls

Got it. Sounds like you're in the market for a SQL database. In your setup, is there anything extra you'd want? I guess I'm merely wondering what FireBase and Co could even provide to you?

Firebase provides the auth, and the fact that it's easy to take a look at the database, but indeed I'd rather use Postgres

Makes sense. If it's mostly auth you're after, there's a bunch of dedicated products: https://github.com/zitadel/zitadel, https://github.com/teamhanko/hanko, https://github.com/casdoor/casdoor, https://github.com/authelia/authelia (At least the first is Postgres compatible)

Reply on news.ycombinator.com