With the size, complexity of the software system either a monolith architecture or frontend and backend architecture or microservice architecture is used mainly. For large complex software systems…

ekangal

Domain-Driven Design

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Micro-frontends is the beginning of the micro frontends journey. The idea behind Micro Frontends is to think about a website or web app as a composition of features which are owned by independent teams. Each team should be able to choose and upgrade their stack without having to coordinate with other teams.

Introduction to Micro-frontends

I would be worried about design consistency though, but interesting idea nevertheless

I’m yet to find a non-trivial example (with implementation details of course) of this idea.
Lots of similar stuff floating around on youtubes and mediums, but those are all built around module federation, and are pretty much just your average webapps with pinned versions of your favorite frameworks but with extra tooling and extra places to break.
Feels like nobody has figured out a generic solution for this. But the promises… yeah, it’s a holy grail we’ll never get to…

One major disadvantage of micro frontends in web development is the added complexity and difficulty in managing and coordinating the various different frontend components