"It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch." If you are using this as a web server persistence back

"It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch." If you are using this as a web server persistence backend, I would agree with the first, more or less accept the second and reject the third. HTTP + JSON serialisation are way slower for that kind of job. If you are just exposing the database using only the Postgres, in that case is interesting, however, I have concerns about how more complex business logics would work with such a CRUD view.