4 ms·
I do use PostgreSQL wherever possibly. Add http://postgrest.com/ http://postgrest.com/ and nginx as a url-rewriting proxy and you have a performant, highly adap
by cel1ne 10y ago
I do use PostgreSQL wherever possibly. Add http://postgrest.com/ http://postgrest.com/ and nginx as a url-rewriting proxy and you have a performant, highly adaptable REST-Server.
- einhverfr 10y agoI know of some relatively high end systems which are doing that, which used postgrest for prototyping purposes and then found it performed too well to give up!
- ruslan_talpa 10y agoHa :)! can you maybe give some links?
- einhverfr 10y agoI think internally the upcoming Kosovo property tax management system will use it.
- ruslan_talpa 10y agoThis is one of those things you frame and put on the wall :)
- BerislavLopac 10y agoNice, Postgrest looks really amazing, especially for long-term production needs. I've previously used Sandman, which is much easier to set up, which makes it ideal for more quick-and-dirty needs: https://github.com/jeffknupp/sandman2 https://github.com/jeffknupp/sandman2
- StreamBright 10y agoMe too, never failed me for the things I use it for. Unlike other data stores, it has predictable, consistent performance, production ready releases, and reasonable opensource contributors who really deliver the awesomeness. Its architecture is unique, at least in the FOSS word.
- vosper 10y agoI looked at Postgrest and liked what I saw, until it came to authentication and authorization - the docs mention that this is an area that tends to blur the line between application and database layer, and then just sort of punts on the whole thing, suggesting that maybe you want to use the auth0 SaaS. Have you had to deal with this?
- icot 10y agoYes, we found the same issue. We worked around this by organizing our application (an admittedly basic REST API) in two layers. The external one exposed to API consumers, developed in a language/framework you may like (Python/Tornado for us), and the internal data access layer which uses Postgrest, and is only accessed locally from within the REST API application servers
- rubber_duck 10y agoWhy not just query the database using standard drivers then ? What am I missing here ?
- spdionis 10y agoMaybe the the exposed application acts like a proxy for the internal apis, only check authentication info and pass on the request to the postgrest servers.
- ruslan_talpa 10y agoI know the docs are lacking but have you guys looked into how roles + RLS + views can work together to solve authorization?
- ruslan_talpa 10y agoYes the docs are lacking but the hope is that the users will get the basic idea and look into things like roles+RLS in the official Postgre docs (although those are lacking too :) it's a very powerful feature, this RLS thing, but since it's new, there are not a lot of examples explaining it)
- drdaeman 10y agoIs there a way to have combined permissions, based on both row and column? For example, considering the `passwd` table example https://www.postgresql.org/docs/9.6/static/ddl-rowsecurity.html https://www.postgresql.org/docs/9.6/static/ddl-rowsecurity.h..., allowing user to select their own pwhash, but no other users' pwhashes. I find owner-dependent field-level permissions to be a fairly frequent requirement.