If you use this, also take a look at GraphQL, AWS has a hosted GraphQL service called Appsync, and if you look into self hosted you can also use Prisma.
It's highly customisable, works directly with postgresql row levels security and the performance is quite good. It has a custom GraphiQL gui to work on queries/mutations.
To really see how it all works together checkout the starter project: https://github.com/graphile/starter it has migrations, job queue, graphql-codegen etc.
tried GraphQL, not sure I'm sold on it viability. Sure it is very uniformed, however for nested queries it is very slow. We already have SQL don't need another querying language in js. If I really want get fancy then prolog would be much more preferred. On top of that FB is backing the project make me feel very uneasy, the same exact reason why I won't want to use React with a 10 foot pole.
(disclaimer: not feeling totally authoritative on this, have not used graphql in production).
i feel that the choice between postgrest & postgraphile / another graphql solution revolves around whether you're a front-end dev who doesn't get to arbitrarily change/expose data schema. if this is true, and you are collaborating with other devs on the code then the added flexibility in querying probably outweighs the inferred complexity of this complex data abstraction.
if, however, you control both back and front-end, graphql isn't really needed, as you can expose whatever views you fancy by means of SQL (via views, table/row permissions, rpc functions exposed by postgrest, etc)