If you had to decide — implement micro-frontends or use monolith — how would you make the decision?

The choice between micro frontends and monolith depends on several factors:

• Size and complexity of the project. If the application is large, with different teams, micro frontends help divide responsibility and speed up development.
• Teams and processes. With multiple independent teams, micro frontends allow them to work autonomously, choosing their own technologies.
• Deployment and update requirements. Micro frontends enable updating parts of the application independently, reducing risks.
• Technical debt and support. Monoliths are simpler to implement and debug initially, but over time can become difficult to scale.
• Performance and user experience. Micro frontends can increase load times due to multiple bundles if not optimized.

If the project is small or medium, the team is small, and there is no urgent need for separation, it is better to start with a monolith. If the project is growing, teams are distributed, and flexibility is needed — micro frontends can be justified.

It is important to evaluate:

• architectural goals,
• organizational capabilities,
• team experience,
• technical constraints.

The decision should be balanced, considering support costs and implementation complexity.