> you have to create a separate schema ("api" or similar) to carefully pick what's exposed. Yep, but it's a CREATE VIEW instead of writing a route in python or

> you have to create a separate schema ("api" or similar) to carefully pick what's exposed. Yep, but it's a CREATE VIEW instead of writing a route in python or ruby which also will likely hit an ORM... > Serving assets from Postgres seems like a bad idea aside from some simple edge use cases. In general, you want to treat your DB as a precious resource and minimize the amount of work it has to do. The database should still be the source of truth (of generated assets). An easy solution is to configure NGINX to cache those asset requests, or write a script to unpack them to the file system.