From the web page: "Application developers should care about data – not SQL" That is fundamentally wrong - or at least - it is very limiting. Think very hard

From the web page: "Application developers should care about data – not SQL" That is fundamentally wrong - or at least - it is very limiting. Think very hard about adopting a framework that tries to shield you from SQL. Because at the end of the day, you will be looking at SELECTS and INSERTS in your logs because you are wondering why things are so slow or why your memory usage skyrockets. It looks like Prisma allows you to go to raw SQL if you must, yet you won't have a good time using some of PostgreSQL more advanced features. If your domain model is simple and will remain simple in the future, then - by all means - use a builder that creates queries from your domain model. Use a single-source-of-truth approach that is usable from the back-end and front-end. In other cases, where your domain model changes over time, be very careful when choosing an ORM but extra double careful in picking the right data store.