As a solo dev/data person, an appeal of PostgREST is that I can effectively encode the database schema and the API schema in the same step. And operationally speaking, it's easy to figure out how the API is configured without having to look at application code or application configs -- just look to the database.
A simple translation layer between the database (to address your worries about indirection) is to create a materialized view for each API endpoint. Need to expose a new column? Easy, just redefine the view. Isolation through schema usage can go really far here also.
Not sure if I would put a production system on PostgREST, but I'd love to hear others' experience if they put it in prod ever.
A simple translation layer between the database (to address your worries about indirection) is to create a materialized view for each API endpoint. Need to expose a new column? Easy, just redefine the view. Isolation through schema usage can go really far here also.
Not sure if I would put a production system on PostgREST, but I'd love to hear others' experience if they put it in prod ever.