> Don't have your core business logic operate over database rows
This is the part where I don't agree, as SQL is very expressive, and needlessly loading data to your app is also not performant (making the transition to something else required sooner).
I think writing parts of your business logic in SQL that make sense to be written in SQL is just fine.
If you only use it to load and write entities, then that is basically a glorified KV store.
This is the part where I don't agree, as SQL is very expressive, and needlessly loading data to your app is also not performant (making the transition to something else required sooner).
I think writing parts of your business logic in SQL that make sense to be written in SQL is just fine.
If you only use it to load and write entities, then that is basically a glorified KV store.