> For the complete documentation index, see [llms.txt](https://getstarted.gitbook.io/micro-frontend/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://getstarted.gitbook.io/micro-frontend/master.md).

# Micro-Frontend

New age Microservice design pattern, for front-end application to decompose a monolithic application into individual semi-independent micro-apps with simple single responsibility, audience-driven, easy to develop and maintain with iterative approach, enable many benefits such as independent deployments, migration and experimentation, and resilient applications. 

Micro Frontend are not trying to replace component architecture rather its a technique that decouple between teams and decentralise responsibility of each feature/capability & controlled separately independent of other team members that are more manageable and independent lifecycle and even stack.

### Decomposed & Iterative approach

With **decomposition**, decentralising decisions to teams, a value-addition for organisation and platforms as team lives and breathe with the product-teams and SME business experts without boundaries and constraints that sometimes are unnecessary. 

Micro Frontend is change-in-game, **Iterative approach** for plan, design and deliverables and technology-independent and allow-s team to deploy pilot solutions and technologies for defined users and parallel implementation on upcoming features and roadmap as teams scope are changed to small rather than full single application.

> **Techniques, strategies and recipes for building a modern web app with multiple teams using different JavaScript frameworks. —** [**Micro Frontends**](https://micro-frontends.org/)

![Evolution of Software Architecture - journey from monolithic application to Microservices and micro frontend.](/files/-Mh1u2GOljIrUJ1o8Kn_)