4 ms·
> When you need to integrate with 3rd parties though you're right back to writing traditional backend code. So now you have extra dependencies and a splintered
by michelpp 6y ago
> When you need to integrate with 3rd parties though you're right back to writing traditional backend code. So now you have extra dependencies and a splintered code base.
Those third parties can still talk to the same database. We use this pattern all the time, PostgREST to serve the API and a whole bag of tools in various languages that work behind the scenes with their native postgres client tooling.
- berkes 6y agoIt sounds like it quickly becomes extremely difficult to change the datascheme then. Do you tightly orchestrate releases? Or do you simply never change the schema?
- GordonS 6y agoDoes PostgREST have functionality for authentication and authorization? I guess you could front it with a reverse proxy if not, but would be nice to have auth built in.
- michelpp 6y agoIt uses JWT, you can use third party or serve them yourself.
- IggleSniggle 6y agoI haven’t used postgREST, but the user/group authorization model looks fantastic at a glance.
- FlyingSnake 6y agoYes, it has first class support for 3rd party auth using signed JWTs. I use it with Auth0 to provide social logins. [1]: http://postgrest.org/en/v7.0.0/auth.html#client-auth http://postgrest.org/en/v7.0.0/auth.html#client-auth [2]: http://postgrest.org/en/v7.0.0/ecosystem.html http://postgrest.org/en/v7.0.0/ecosystem.html
- SahAssar 6y agoI use caddy-auth-portal and caddy-jwt to generate JWTs for AuthN (based on SSO) and then use postgres built in row level security for AuthZ.