Member-only story
10 Decision Points for a Micro-Frontend Approach
How do you decide whether micro-frontends are right for your project, and if so, how do you proceed?
In an era where certain JavaScript frameworks become out of favor at lightening speed, frontend developers are busy rewriting applications using new, emerging ways all the time.
We are desperately searching for a possibility to jump onto the latest and greatest things, without worrying about the baggage of legacy code. In simple terms, we want to decouple components. This appealing idea is called micro-frontends.
What is the micro-frontend approach? The term micro-frontend first came up in the ThoughtWorks Technology Radar in November 2016. It extends the concepts of microservices to frontend development.
This approach is to split the browser-based code into micro-frontends by breaking down the whole application. Sub-application is likely implemented by a vertical team from backend to frontend. This ensures that every sub-application is independently developed, tested, and deployed.
We adopted Cam Jackson’s micro-frontends approach in our projects. Based on our first-hand experience, we would like to share ten decision points for micro-frontends.
