4 ms·
"integrates UI, business logic, and storage" There are solid reasons why we don't do this. Just to name one: a single database table rarely holds the informati
by bradley13 3y ago
"integrates UI, business logic, and storage"
There are solid reasons why we don't do this. Just to name one: a single database table rarely holds the information you need, and is even less likely in the way you want the user to see it.
- GMoromisato 3y agoIt's orthogonal, in my view. You can integrate UI, business logic, and storage without forcing everything to be one table. You can, of course, have multiple tables in your app. Moreover, you can decouple the UI schema from the table schema. But if you can put it all in one schema, why not?