A curated list of resources about everything Micro Frontends
Clone or download
ChristianUlbrich Merge pull request #1 from naltatis/patch-1
Fixing the micro-frontends.org link
Latest commit e88432d Jan 4, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitattributes initial version Oct 29, 2018
.gitignore initial version Oct 29, 2018
.nvmrc initial version Oct 29, 2018
README.md Fixing the micro-frontends.org link Jan 4, 2019
code-of-conduct.md initial version Oct 29, 2018
contributing.md initial version Oct 29, 2018
package.json initial version Oct 29, 2018


Awesome Micro Frontends Awesome

A curated and hopefully awe-some list about Micro Frontends.


Micro Frontends are an architectural pattern, just as Microservices are. There are many ways to achieve a Micro Frontend architecture. This list presents the essential and required material to come up with your very own Micro Frontend approach.

In this approach, the web application is broken down into its features, and each feature is owned, frontend to backend, by a different team. This ensures that every feature is developed, tested and deployed independently from other features. Multiple techniques exist to recombine the features — sometimes as pages, sometimes as components — into a cohesive user experience. Source



Blog posts and web sites that are talking about the general concepts for a Micro Frontend architecture.



Building Blocks

Web Components

  • Custom Element V1 - The Custom Elements V1 API is the most important API you need for building Web Components
  • StencilJS - StencilJS is a specific framework for building Web Components declaratively with modern TypeScript.
  • LitElement - super-recent small library from Google to bootstrap Web Components

Event Bus

  • Postal.js "loosely AMQP inspired EventBus for the browser"


  • unpkg.com - allows for deep-linking into the npm registry and thus to consume components off npm


  • Mosaic - Project Mosaic is Zalando's take on micro frontends and is a complete framework for it.
  • single-spa - Canopy's approach on micro frontends is about composing multiple SPAs.
  • OpenComponents - "an open-source, "batteries included" micro frontends framework"
  • Polymer Project - Google's take on building Web Components that still has some nice tooling


  • Polymer Project - Google's take on building Web Components won't be used for its upcoming Material Web Components and that says it all


Other Lists



Contributions welcome! Read the contribution guidelines first.



To the extent possible under law, Christian Ulbrich has waived all copyright and related or neighboring rights to this work.