I really like the Single-SPA development experience. But I think there are requirements and use cases which leads to choosing the micro frontend architecture. For example, you /can/ implement SSR and Single-SPA, but then you need to decide on details. On the other hand, if you use something like NextJS there is already a nice ready-made interface to add SSR and SSG to your app. But by using NextJS you are tied to using only one framework, React. There are also more opinionated ideas and frameworks which are not compatible with Single-SPA which you may want to pick.
So there are trade-offs. If the project is small enough to be planned, developed and maintained by one team and the team is confident enough in choosing a framework, I would choose a framework with less complexity. But in a case where you need the features that Single-SPA provides, i.e. having fully independent micro-frontends maintained by separate teams with separate codebases, release cycles and frameworks, Single-SPA is ideal.
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.
@altjeno
Hi! Thanks for taking your time!
I really like the Single-SPA development experience. But I think there are requirements and use cases which leads to choosing the micro frontend architecture. For example, you /can/ implement SSR and Single-SPA, but then you need to decide on details. On the other hand, if you use something like NextJS there is already a nice ready-made interface to add SSR and SSG to your app. But by using NextJS you are tied to using only one framework, React. There are also more opinionated ideas and frameworks which are not compatible with Single-SPA which you may want to pick.
So there are trade-offs. If the project is small enough to be planned, developed and maintained by one team and the team is confident enough in choosing a framework, I would choose a framework with less complexity. But in a case where you need the features that Single-SPA provides, i.e. having fully independent micro-frontends maintained by separate teams with separate codebases, release cycles and frameworks, Single-SPA is ideal.