Micro Frontends Conference

Micro Frontends Conference

Improving front-end architecture practices.

Make a submission

Submissions are closed for this project



Micro Frontends (MFEs) is quite a popular term in the frontend community. At times, it is also an over-used term. There are multiple schools of thought in the community, ranging from why MFE are the best suited for architecture for frontend development, to why MFE is a huge mistake.

Like all things in software development, the answer to “Is Microfrontends right for me?” is … it depends. In this conference, we will unpack the various elements of MFEs, and hear about the joys and pains from people who have built MFEs.

JSFoo track on MFEs is curated by Vinci Rufus, VP of Technology at Publicis Sapient.

Key takeaways:

- Better understanding of what MFEs really mean.
- Tools and tech stacks that are commonly used for building MFEs.
- Connect with some of thought leaders in the MFE space.

Who should attend:

- Frontend engineers building web apps on modern Javascript frameworks.
- Mid to senior developers building large scale applications.
- Senior Architects, CIOs and CTOs at startups and product companies who are evaluating using MFEs.

Who should speak:

We seek experiential and deep dive technology talks from individuals who are architects or frontend leads, who are either exploring or have built and deployed applications on a micro frontends architecture. See submission guidelines at https://hasgeek.com/jsfoo/microfrontends-conf/sub

Schedule: https://hasgeek.com/jsfoo/microfrontends-conf/schedule/

Contact information:

For inquiries about speaking or participating in the conference, post a comment at https://hasgeek.com/jsfoo/microfrontends-conf/comments
For more updates, follow JSFoo on Twitter

Hosted by

JSFoo is a forum for discussing UI engineering; fullstack development; web applications engineering, performance, security and design; accessibility; and latest developments in #JavaScript. Follow JSFoo on Twitter more

Supported by

The Notification Inbox for your product. YC-W21 more


Rajasegar Chandiran


Framework Freedom with Micro-Frontends

Submitted Dec 7, 2021

Can we use multiple JavaScript frameworks in a single-page application? Yes, it is possible with Micro-Frontends. In this talk we are going to explore what are the different ways you can make multiple frameworks like React, Vue and Angular live in harmony in an SPA and also allow you to split the code by functionality. We also discuss on why autonomy matters more for a team to choose their own tech stack for better and faster feature rollout instead of forcing them to use ineffective and older technologies.

Slides: http://framework-freedom.surge.sh

The Freshworks story

  • One flagship product to more than 7 products and 100s of platform services
  • 50K+ customers
  • Ruby on RAILS to Java, Go, Ember.js, React and so on
  • Most products are monolithic codebases

The Unified Product Experience

  • Our business wanted to integrate different product experiences into an unified experience for the customers.
  • Bundled products is the future
  • Looking at infinite permutations and combinations for product UI experiences and capabilities
  • Engg. vision needs to be aligned with business mission and product roadmaps.

No More Iframes

  • Legacy way of integration among different product and platform services
  • Security
  • Performance
  • Accessibility
  • Authentication hassles and overhead

Why Microfrontends?

Optimize of Feature development

Make Front-end upgrades easier

Increase customer focus

Why you want to use multiple frameworks?


  • Support agility by allowing teams to choose their own technology
  • Lot of acquisitions means different tech stacks


  • Major concern with monolithic codebases
  • Faster landing pages are crucial for business success
  • Rewriting a slower module with a better and faster framework of choice

Diversity in Technology

  • Putting all your eggs in one basket
  • Don’t build all your products with one framework
  • Betting on potential framework alternatives for the future
  • Diversification is not only good for money but also for technology

Microfrontends Composition

  • Client-side composition
  • Server-side composition
  • Pros and cons

Client-side composition

  • Because our existing product experiences are SPAs


  • JavaScript router for front-end microservices
  • client-side routing
  • JavaScript modules for integration at the browser
  • Rich eco-system of tooling and libraries
  • Helpful and broad community support
  • Plugin architecture
  • Different type of Micro-frontends for different use-cases

Challenges with MFEs

  • 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 MFEs

## Key takeaways

Participants will learn

  • how to use multiple frameworks in a single-page application
  • what are the ways of effective communication between different micro-frontends
  • how to promote autonomy among teams to choose the best tool for the job


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Swaraj Cheguri

Micro Frontends a Hybrid approach

In the world of current Micro Frontends eco system there are several ways where one can achieve the task of running different independent apps as one app, or in other words implement micro Frontends Architecture. We at Harness wanted to build our own framework/ approach which combines best of all the exisiting approaches and at the same time not depending on any particular third party library to … more

08 Dec 2021