Using Phoenix as a "kitchen sink" web framework vs a lightweight toolkit?

[axelson]

@NobbZ

It basically says, a database is not needed, use a database instead, as a database is just a service. A service that is built to store data.

What I might agree with though is, the presentation layer does not necessarily need to know where and what DB is actually used, but instead should retrieve and store data only through an abstraction layer. In phoenix this layer is called “contexts”.

I believe that what Dave is advocating for is similar to what you’re saying in your second paragraph. However his approach is to split the business logic/persistence and the web interface into two separate applications, rather than using Phoenix Context’s to keep them in the same application but in different “namespaces”.