Here I have Curated tutorial and resource links on the micro frontend, meant to be a collection of high-quality articles and resources for someone who wants to learn about the Micro Frontend, as well as a source for quality information on advanced topics and techniques. Not quite "awesome", but hopefully useful as a starting point, I can give to others. Your suggestions always welcome.
- An architectural style where independently deliverable frontend applications are composed into a greater whole.
- Scaling frontend development so that many teams can work simultaneously on a large and complex product is even harder.
1. Micro Frontends By Cam Jackson
- Good frontend development is hard. Scaling frontend development so that many teams can work simultaneously on a large and complex product is even harder.
- In this article we'll describe a recent trend of breaking up frontend monoliths into many smaller, more manageable pieces, and how this architecture can increase the effectiveness and efficiency of teams working on frontend code.
https://martinfowler.com/articles/micro-frontends.html
- The idea of Micro Frontends is to break down the frontend monolith into smaller, more manageable pieces. Each team can own its own features end-to-end, work in their own codebase, independently release versions, constantly deliver small incremental upgrades, and also integrate with other teams via APIs so that they can compose and manage pages and applications together.
https://itnext.io/11-micro-frontends-frameworks-you-should-know-b66913b9cd20
- At Bit, They build tools for over 100,000 developers working with components. Our tools help developers build, reuse, and collaborate on independent components to speed up development and improve application quality.
https://blog.bitsrc.io/how-we-build-micro-front-ends-d3eeeac0acfc
- The main goal of microfrontends is isolation: Individual small applications that form a larger system together are to be implemented independently of each other.
- This means that a small team can take care of each application. Since these teams are self-sufficient, they do not need to coordinate with each other and can deliver business value as quickly as possible.
- This is why it is also common to place microfrontends in their own repository. While this brings isolation, it also creates extra work managing and sharing libraries. Monorepos, on the other hand, which accommodate several microfrontends, make these tasks easier.
https://javascript-conference.com/blog/microfrontends-in-the-monorepo/
- Federated applications are a superset of micro frontends that can enable them, but also other architectures that benefit from dynamically sharing code between independently deployed applications—some of which will be discussed in this article.
- Module federation introduces a few new concepts that are worth explaining before going deeper.
https://rangle.io/blog/module-federation-federated-application-architectures/
Micro Frontends Architecture Patterns Series' Articles - https://dev.to/okmttdhr/series/10191