> using a giant solve all your problems web framework (Phoenix) Other people have said the same thing, but I want to echo the point that Phoenix doesn't need t

> using a giant solve all your problems web framework (Phoenix) Other people have said the same thing, but I want to echo the point that Phoenix doesn't need to be used as a large framework. I work on a large, production Elixir app, and all of our business logic is implemented as separate apps that don't even include Phoenix as a dependency. They're just structs, modules, functions, and supervision trees. We then depend on those apps from our various frontends (web, api), which is where the Phoenix integration happens, and at that point it's more or less just template rendering and routing.