DEV Community

Discussion on: Micro frontends: my lessons learned

Collapse
anfibiacreativa profile image
Natalia Venditto Author • Edited on

Thank you! and ....Exactly!!! Which then makes you really wonder if you truly need microfrontends in the first place :D

Collapse
layzee profile image
Lars Gyrup Brink Nielsen • Edited on

I strongly agree. If you're going to use the same framework, a well-structured monorepo will help you a lot more. It should allow teams to work in isolation, only test, build, and deploy according to what has changed in their commits. It should guard them from making deep imports.

The only real use case for most organizations in my mind is if feature modules are not known at build time. JavaScript itself is very dynamic and even allows arbitrary dynamics imports. Out build tools and compilers are the issue here. Recently, a build tool provided a solution for a problem it introduced itself. Webpack Module Federation. This is just scratching the surface. Microfrontends bring a lot of complexity and challenges as mentioned in this insightful article.

Thread Thread
anfibiacreativa profile image
Natalia Venditto Author

100% agreed, Lars. Monorepos are definitely the way to go!