When Micro-Frontends Aren’t the Right Choice _ by Szymon Chudy
Micro frontends are definitely a trending topic. They receive significant attention by promising better separation of concerns, team independence, and ultimately – quicker delivery. But after years of excitement, I found myself recommending against them. Here’s why.
Preface Micro frontends are definitely a trending topic. They receive significant attention by promising better separation of concerns, team independence, and ultimately - quicker delivery. But after years of excitement, I found myself recommending against them. Here’s why. This article was featured in Issue #16 of the Micro-Frontends Newsletter by Luca Mezzalira - Principal Solutions Architect at AWS, an international speaker, an O’Reilly author and LinkedIn Top Voice. It’s Not a Rant Despite the title, this article is not about ranting. In fact, it’s quite the opposite. When I first read Bui
Explore this link on the map →related reading
- Micro Frontends - extending the microservice idea to frontend developmentmicro-frontends.org
- How Vercel adopted microfrontends - Vercelvercel.com
- From Monolith to Microservices to Reasonably-sized Servicesperandrestromhaug.com
- You probably don’t need microservicesthrownewexception.com
- Choose Boring Technologyboringtechnology.club
- Microservice Trade-Offsmartinfowler.com
- Cognitive load is what mattersminds.md
- Which web frontend architecture fits best?workingsoftware.dev
- Navigating the future of frontendfrontendmastery.com
- The new wave of Javascript web frameworksfrontendmastery.com
- Sam Newman - Backends For Frontendssamnewman.io
- Microservices: Decomposing Applications for Deployability and Scalability - InfoQinfoq.com