DEV Community

Discussion on: Are micro frontends still a thing?

Collapse
 
roxberry profile image
Mark Roxberry

Not sure that anything has faded (your post referenced an article from only a few months ago). I'm seeing more reference works, published code and discussions and heads down work in progress (community is in a flow state, maybe). Has architecture adapted to MFEs realized?

I'm working with both Single-SPA and Webpack Module Federation and view an MFE architecture as a fit for products, systems that are developed by multiple teams (read Team Topologies), aligning with the "developer as a service" reality.

  • Platform services, control plane are developed, promoted by our core platform group.
  • Vertical splits for our business sub domains, with flexibility on the tech stack for those sub domains and developed by "stream aligned" teams.
  • Horizontal splits, case by case.

I like the flexibility in the team formation, not handcuffed to a static job req, technology stack. I think more work in the service / module discovery tooling needs to be done with more top down exemplars, for an opinionated platform architecture. I think we are not at a point that we agree on what are the best practices of an MFE architecture - more work needed.