micro-frontends.org

What It Is

micro-frontends.org is a developer reference site that explains the architectural ideas and practical techniques behind “micro frontends.” It is not a traditional SaaS product or CLI tool. It extends the microservices principle of splitting systems by business capability and enabling teams to ship independently into the frontend, with the goal of preventing large SPAs from turning into hard-to-maintain Frontend Monoliths. The article uses a tractor store example to show how multiple teams can separately own fragments such as checkout, recommendations, and product pages.

Core Capabilities and Technical Dimensions

The site’s core value lies in its architectural methodology. It emphasizes being technology-stack agnostic, isolating team code, using naming prefixes, favoring native browser capabilities, and building resilient websites. On the implementation side, it uses Custom Elements as the integration boundary between teams, with tag names, attributes, and events forming the public contract; Shadow DOM is used to isolate styles and markup; and CustomEvent plus DOM Events are used for communication across fragments.

In terms of supported languages and frameworks, the examples use JavaScript, Node.js, Express, nginx, and Docker Compose. Because the approach is based on Web standards, the article explicitly notes that mainstream frameworks such as React, Vue, Angular, Svelte, and Preact can all embed or publish Custom Elements. The server-side composition section introduces SSI and also mentions alternatives such as ESI, nodesi, compoxure, and tailor.

Pricing and Open Source

The website content is free to access, and the source code is hosted at neuland/micro-frontends and generated with GitHub Pages. The examples can also be run locally via git clone and docker-compose. However, the main text does not specify a license, nor does it mention enterprise support or commercial subscriptions. The page refers to the companion book, Micro Frontends in Action, which can be purchased from Manning, Amazon, or bookstores, but no pricing is listed.

Pros and Cons

The main strength is that the content is highly focused on real architectural concerns: page composition, server-side rendering, progressive enhancement, skeleton screens, communication, and team boundaries are all discussed, without being tied to a single framework. The downside is that it is not a ready-to-use platform: there is no console, hosting, monitoring, or permission management. Examples involving SSI, nginx, and multi-service composition may present a learning curve for beginners, and the documentation is closer to a long-form article plus reference application than a complete product manual.

Who It’s For and Access from China

It is suitable for frontend architects, large Web application teams, organizations that need multiple teams to independently release frontend features in a microservices context, and teams looking for a reference when gradually migrating legacy frontends. The source text does not provide information about access from China, so actual network conditions should be checked in practice. Payments are only relevant to third-party book purchases; users in China may want to consider local network conditions and bookstore availability. If you need a more engineering-oriented framework, you can compare it with options such as single-spa, qiankun, and Module Federation.