Micro-frontend Architecture


An introduction into the new age of front-end development .

What is Micro-frontend actually?

A micro-frontend architecture is not something new in the developer community. In fact, many of you might already be using this in your own development teams to a certain degree. how to get ivermectin in the us

In a nutshell, a micro-frontend architecture is a development architecture in which you would have your different frontend components split into separate streams. Think of a micro service, instead of having one web method to communicate between your frontend and backend, you split it into separate micro services that are each responsible for one function.

Tell me more…

Let’s look at it in a more practical example. We all know of Netflix, and most of us spend our weekends binging tv series they offer (btw if you haven’t yet watched “The Witcher”, you’re wasting your life).

So as you can see, the Netflix UI has many components that make up what the users sees. ivermectin oral dosage goats However, if we look at each highlighted block, we can see just how it is broken up. For instance, the “Trending now” slider is a separate micro-frontend with each individual “Tile” being another separate micro-frontend. Each micro-frontend serves a purpose and together they form the grand front-end.  

What’s interesting and one of the many benefits of using this architecture is that each component (let’s call them features) is managed by a separate team, and built independently of each other. This allows for your different feature teams to build, test and deploy code faster, and also prevents there being one centralised code-base, which can be tedious to maintain. This also allows teams to easily share components among each other, increasing productivity and reducing developers from trying to build and reinvent what’s already there.

Another huge benefit from adopting this type of architecture is that it allows developers to work in whichever framework they choose. One team could use Angular for the Carousel feature, whereas the team responsible for the search feature could use React if they wanted.

Ok, I’m listening…

Let’s take a look at the diagram below and get a better understanding.

This diagram represents a basic blog, with a header, sidebar navigation and a section for serving blog content.

There will be a separate team that builds and maintains just the header micro-app. They can use whatever framework they want, have it run in a separate container or Lambda, completely independent of the navigation micro-app and content micro-app. If any changes need to be made to the header, that team can simply make the change, test and deploy without depending or disrupting any other streams.

This is just a basic understanding of the concept of micro-frontend architecture, I am planning on followup on this post with additional posts on Adopting a micro-frontend architecture, things to avoid and even a series of building a simple application using this type of architecture. ivermectin for dogs demodex mange

If you guys want to know more about micro-frontend architecture, or have any questions, feel free to contact us via our website or social media platforms. Cheers!

About the Author