Hmmm again I’m not sure what your scenario is since I think we are talking about the same thing :) A Feature Module is just a “module which is not the AppModule”, which can be: CoreModule, SharedModules or the one that I call the “View Module”, which is a module that exposes one smart component composed from other components (that can belong to the same module or be part of a uikit/shared module), and obviously must be used in a router path. It’s absolutely correct to use other Feature Modules for business logic only, for example creating an AuthenticationModule if things get complex. Using modules directly into the router path instead of using components is only an advantage, because you’ll have full separation of concerns AND the module can be lazy loaded, so it won’t impact on your app until the route is viewed! And also, there should be only a bit of business logic in your smart components, all they have to do is to grab data from services and passing it down to child components. This way, if you organized your app properly, there’ll be no problem with “upgrading” to a state management library such as Redux.