So I am working on a project currently which the complexity and performance has made me to dive into understanding micro-frontend applications; and I have decided to share with you, as always, my journey pace.
What are Micro-Frontend Applications?
Yes, basically that will be the first question.
Micro-Frontend Application, from my current understanding, is a sublet of an application that can be tested and run independently, and with run efficiently when fused in with the larger application.
The concept of micro-frontend application is actually interesting, quite interesting than I thought it would be when first diving in. Imagine being able to write different mutually independent application in there different languages and still be able to run them together as one single application? That's a wow!, for me! I DON'T know of you, though.
Types of Micro-Frontend Applications
Of course, looking at how the software industry as grown, there definitely are going to be different kinds of methods of adapting into the micro-frontend applications approach. According to a lecture given by Academind (link in the references section later) there is currently no standard approach to developing micro-frontend applications.
However, when looking at single-spa, there are three kinds of micro-frontend application approach in spa:
- Application - when a chunk of UI is rendered for a specific set of location routes
- Parcel - when a chunk of UI is manually rendered by the an application
- Utility module - this is when there is a shared common JavaScript logic, but no rendering
References
To be available soon
Acknowledgement
Thanks for engaging! 🎉