Micro Frontends

Microservices are a well established pattern in backend development. Everybody is using it. Running more than a dozen of microservices just to handle a single domain is not uncommon. But when it comes to frontend development, things are often different. I experienced two situations a lot:

One random day not long ago, I started hearing joke after joke about "micro frontends" — sort of how I first learned about Toast. I didn't understand

Solving hard problems, DOM performance, keeping up with the JS ecosystem, and much more.

We've seen significant benefits from introducing microservices, which have allowed teams to scale the delivery of independently deployed and maintained services. Unfortunately, we've also seen [...]

Stacker is the backbone of our implementation of Micro Frontends.

Summary # Figure 1: “Building Microservices (2nd edition)” along my notes During my overall IT carreer I came across different architectural design patterns where oppinions differ on the question if they’re the right ones for the problems/challanges teams are dealing with. Before reading this book I was familiar with some of the microservices concepts but it was some article (on modern architectures) that rouse my attention and introduced me to Sam Newman.

Over the course of just a few quarters, a micro-frontend platform radically improved the speed with which teams could deliver and iterate on web UI, and radically shifted the ownership model of that UI. But it wasn't without pitfalls to avoid.

Modularity is a crucial concept when designing and creating software. Independent of whether our chosen architecture style is to have a single unit of deployment - Monolith or multiple units of deployment - Microservices/Services. It is a quality that should be treated completely independent of how many deployable units of software we choose to have.

A modular methodology implemented at Roundforest to improve developer velocity for large scale codebases

Reflections on how a complicated technology setup can be made to work for the team instead of against them.

A structured approach to designing and documenting each of your bounded contexts - ddd-crew/bounded-context-canvas

Techniques, strategies and recipes for building a modern web app with multiple teams using different JavaScript frameworks.

Principal Serverless Specialist Solutions Architect at AWS, International Speaker, O'Reilly author, Content Creator

As our suite of products has grown from a website builder and commerce tools to encompass much more, synchronizing frontend state across these products has become increasingly important. Complicating the matter, some products run in iframes, whereas others run in the main browser window. We’ve devel