“As a more distributed architecture, micro frontends will inevitably lead to having more stuff to manage - more repositories, more tools, more build/deploy pipelines, more servers, more domains, etc.” In the same post, Cam Jackson hits the nail on the head by asking, “Are you comfortable with decisions around tooling and development practices becoming more decentralised and less controllable?”¹

Similarly, challenges abound with adopting micro frontends in the Indian context. For example, Rajasegar Chandiran shares some of the challenges with using micro frontend architecture at Freshworks:

Working with a unified URL
CORS
Deployments - Blue-green
Reusing components across frameworks
- Common UI components
- Common Library Code (Sharing same React version across different MFEs)
Communication with different micro frontends²

The micro frontends conference - curated by Vinci Rufus - brings experience of success, failure and that state in between - with adopting micro frontends in organizational contexts such as Uber, Myntra, Harness and Freshworks.

Meanwhile, follow JSFoo on Twitter to stay updated about the upcoming Twitter chats on different aspects of micro frontends (including some yay and nay trolling!!!).

References and sources:

Source: https://martinfowler.com/articles/micro-frontends.html ↩︎
Framework Freedom with Micro-Frontends -
https://hasgeek.com/jsfoo/microfrontends-conf/sub/framework-freedom-with-micro-frontends-KstpkeuAwcKjKGujGH3HKh ↩︎

CSS loading and Critical CSS

{{ gettext('Draft') }}