Using a database as a backend comes up time and again and developers are sharpely divided over this concept. I feel that developers who started their careers be

Using a database as a backend comes up time and again and developers are sharpely divided over this concept. I feel that developers who started their careers before the advent of NoSQL DBs/MEAN stack/etc had to go through the rigor of fine tuning their SQL queries and witness the powers (and quirks) of a performant SQL DB. These devs are usually a fan of using DB-as-a-backend. Personally, I am a big fan of PostgREST and I apply it whenever I find a use case that suits it. I find it quite pragmatic and it just shines when it plays to it's strength. Pragmatic developers should took a pragmatic look at such approaches and try to use the powerhouse that are SQL DB engines. Shameless plug: I've written an article to showcase it's philosophy and how easy it is to get started with PostgREST. [^1]: https://samkhawase.com/blog/postgrest/postgrest_introduction/ https://samkhawase.com/blog/postgrest/postgrest_introduction...