Awesome post! I would, however, add to the list that "mixing technologies together" is not equal to microfrontends. A monolith on the server-side could have also shipped with multiple technologies. The key points are independent development, deployment, and isolation.
While Single SPA may be (e.g., for migration purposes) a good solution I would love to advocate the solution we've been working on for the past few months (actually, its a generalization of an architecture we implemented for several customers in the last ~3 years): we call it Piral.
Piral is an open-source framework for modular frontends, which focuses on developer experience - leveraging totally independent teams. We just presented it for the first team last week at O'Reilly's Software Architecture Conference in Berlin.
Any feedback appreciated!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Awesome post! I would, however, add to the list that "mixing technologies together" is not equal to microfrontends. A monolith on the server-side could have also shipped with multiple technologies. The key points are independent development, deployment, and isolation.
While Single SPA may be (e.g., for migration purposes) a good solution I would love to advocate the solution we've been working on for the past few months (actually, its a generalization of an architecture we implemented for several customers in the last ~3 years): we call it Piral.
Piral is an open-source framework for modular frontends, which focuses on developer experience - leveraging totally independent teams. We just presented it for the first team last week at O'Reilly's Software Architecture Conference in Berlin.
Any feedback appreciated!