Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Convenient micro frontend framework?

Which is the best approach/framework for micro frontend development?

I have more than 5 apps based on angular, react and vue and want to display all 5 apps on a single UI. We have many micro frontend frameworks like single spa, piral, moisaic project, Podium and many more.. available in market now.Need a clear picture which help me to achieve it using any framework.

microservices #frontenddevelopment

like image 619
Zeeshan Avatar asked Jan 09 '20 08:01

Zeeshan


People also ask

Which is the best micro frontend framework?

Bit. One of the most popular frameworks when it comes to micro frontends is Bit. It is a product-ready solution for building micro frontends. Besides the ability to create, Bit offers the possibility to manage frontends through independent component.

Which front end frameworks are easier?

js is one of the simplest and most straightforward frontend frameworks. It is relatively small in size but does have a virtual DOM, a component-based architecture, and two-way data binding. All of these elements lead to great performance and ease the work associated with updating components and tracking changes.

What is micro frontend framework?

Micro frontends are a new pattern where web application UIs (front ends) are composed from semi-independent fragments that can be built by different teams using different technologies. Micro-frontend architectures resemble back-end architectures where back ends are composed from semi-independent microservices.


1 Answers

It all depends.

Obviously, I am biased towards Piral, but in order for Piral to be efficient you'll need to check some (the more, the better) of the following bullet points:

  • [ ] You want an app shell (either for technical reasons, e.g., provide shared dependencies and / or for other reasons such as a shared / centrally governed design)
  • [ ] You have a clear tendency towards React (i.e., you have lots of different frameworks, but the majority of your apps is written in React)
  • [ ] You need to have components in components (e.g., a component from microfrontend A should be used in a page from microfrontend B)
  • [ ] Your application is "dynamic" / has a "tool" (or application)-like character; no-JS is not a requirement
  • [ ] You want to enable / disable modules on the fly (e.g., certain users should only see microfrontend A, but not B)
  • [ ] You'd love to have rich tooling support, e.g., when scaffolding a new module - and TypeScript support should be first-class, too
  • [ ] Lazy loading (not only of full microfrontends, but of individual components such as pages) should be possible
  • [ ] Communication via the different modules is never direct, but always indirect (i.e., your system will never break if microfrontend A is there, but microfrontend B is not)

The others you mentioned have similar lists.

Hope that helps!

like image 189
Florian Rappl Avatar answered Nov 10 '22 01:11

Florian Rappl