It'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 ta

It'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?