Thisarticlewas originally published on.cultbyDoug Neale.
.cult is a Berlin-based community platform for developers.
If youve ever worked on a large codebase, youll know that it can suck.
Their highly-coupledcodeand increased deployment risk can slowdeveloperproductivity right down.
To combat this, many have shifted away from monolithic applications to smaller, more manageable pieces through microservices.
However, this has largely only affected the backend world while frontend codebases with their ever-increasing complexity remain monolithic.
What are micro-frontends?
It’s free, every week, in your inbox.
A notable example of this is the Spotify client.
If youve got the Friends Activity sidebar open, that would be a third micro-frontend.
Why use micro-frontends?
More important than the how is the why.
And there are many reasons why a company should consider a micro-frontend approach to their frontend codebase.
Having smaller applications dedicated to certain features allows teams to work on relevant code in isolation.
Then they can worry less about how changes affect other parts of the product.
After this is complete, any future upgrades to the stack can also be implemented incrementally.
Every dev knows how fast the frontend world moves you know these upgrades will come.
Increases developer productivity
You may be thinking this all sounds unnecessarily complex.
Some code duplication and boilerplate are naturally going to occur between micro-frontends Luca Mezzalira admits that.
But hestressesthat, when making decisions, its important to consider the context of that decision.
For many situations, the benefits of micro-frontends outweigh this overhead.
Story by.cult
.cult by Honeypot is a Berlin-based community platform for developers.
