4 ms·

I don't see what's so bad. Seems like it would be a convenient way to skip some boiler plate back end code used for CRUD. Probably not optimal for a complex app

by jjice 6y ago

I don't see what's so bad. Seems like it would be a convenient way to skip some boiler plate back end code used for CRUD. Probably not optimal for a complex application, but it looks very neat for something quick and small.

Thaxll 6y ago
If you're learning backend services, don't start by things like postgREST, it's just bad habbit, would be better to start by the basis with API servers / DB ect ...
- emteycz 6y ago
  As a seasoned TypeScript backend/fullstack developer I don't understand - why is it such a bad tool, and if it is because of the tool and not the concept, it seems possible it will be fixed in the future - why is it a bad habit; I consider the boilerplate CRUD code I write to be a bad habit that I should've automated years ago, and that's exactly what PostgREST does - why can't you learn the basics of API services and databases with PostgREST
  - Thaxll 6y ago
    It's a bad habit because of separation of concerns.
    - emteycz 6y ago
      You're not forced to write your app code in the DB as SQL procedures, you can also write TS or whatever else and use it next to PostgREST.
    - steve-chavez 6y ago
      Check this thread[1] for a previous discussion about "separation of concerns" and PostgREST. tl;dr: business logic can be done with views/sps on an isolated schema. More layers makes the overall OLTP system less performant and harder to scale. [1]: https://news.ycombinator.com/item?id=21438307 https://news.ycombinator.com/item?id=21438307