Masterclass Clean Architecture Front

And if we did Clean Architecture on the front side?

Right now, there is a lot of talk about good practices and good questions to ask yourself about a product's architecture: should I do clean/hexa/onion archi, how far to push the DDD, etc. The front is often considered as a "simple" component belonging to this global architecture, and the reflection is go first to the backend and system side.

However, the front code itself has become more complex over the years, with an big increasing of business considerations (whether we like it or not), located in the same code base of UI components, HTTP requests, various business rules, etc. This growing complexity is made possible by (or due to someone will say) the higher number of javascript frameworks/libs and their ecosystems: state management, routing, UI kits, SSR etc. and products with ever more complex features.