5 ms·
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 a
by trailbase 2y ago
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?
- oulipo 2y agoYes, 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
- trailbase 2y agoGot 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?
- oulipo 2y agoFirebase provides the auth, and the fact that it's easy to take a look at the database, but indeed I'd rather use Postgres
- trailbase 2y agoMakes sense. If it's mostly auth you're after, there's a bunch of dedicated products: https://github.com/zitadel/zitadel https://github.com/zitadel/zitadel, https://github.com/teamhanko/hanko https://github.com/teamhanko/hanko, https://github.com/casdoor/casdoor https://github.com/casdoor/casdoor, https://github.com/authelia/authelia https://github.com/authelia/authelia (At least the first is Postgres compatible)