Micro Frontends & Customer Experience - Part I

Imagine you are a customer trying to book a ✈️ flight. You enter the application flow, and successfully book your flight (Yay! 👏)


Before your flight date, you are probably wanting to check things like:

  • Flight status (to check for any potential delays)
  • Payment status
  • Ticket information (old school, in case you prefer to print @ home)

Only thing is, all of that information is accessible through separate Single-Page applications.

Like shown here:

Note: *SPA is shorthand for Single-Page Application.

This Monolithic application architecture requires you, as the customer, to jump from application to application to check for various pieces of information (flight status, payment, ticket, etc.).

This frenzy of application hopping in order to check other flight details creates a disjointed and unguided customer experience.

Just imagine having to bookmark all of these different URLs, since there is no unified alerts/notification option for customers. 🥴

Hello, Micro Frontends! 👋🙂

Implementing a Micro Frontend architecture can help solve this problem.

Join me in Part 2 of my new Micro Frontend series to see how we can fix this!

Disclaimer: In general, I am not for or against monolithic or micro frontend architectural styles. Each application is unique, and one style does not fit all. Some are better suited to be monolithic, some micro frontend, and some fit other patterns.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Abdul Wahab

Abdul Wahab


Multi-disciplinary Software Engineer specialized in building products users love. Today, I manage & secure big data in the cloud. All views shared are my own.