AJR/TechradarDev
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: rename micro-frontends to microfrontends

Browse Source 
There seems to be an internal issue with next.js, redirecting to `techradar/techradar/methods-and-patterns/micro-frontends/`
This commit is contained in:
Mathias Schopmans
2024-04-18 08:00:20 +02:00
committed by Mathias Schopmans
parent df0cc3a950
commit e5738950cf
5 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
radar/2018-03-01/microfrontends.md Normal file
View File

@@ -0,0 +1,17 @@
---
title: "Micro Frontends"
ring: assess
quadrant: methods-and-patterns
---
We see many benefits in Microservices – especially in large teams – but often this architecture
does not involve the user interface. Instead, you might end up maintaining a frontend monolith. With Micro Frontends
you enable your frontend developers to gain the same benefits that we have grown accustomed to in a Microservice architecture:
Decoupled components, which are developed and deployed by independent teams. But what sounds reasonable comes with
challenges. Integrating different Frontends on the client- or server-side can be tricky, as well as keeping the overall
User Experience consistent.
Despite the challenges, Micro Frontends help us to develop large applications across multiple teams. Developers can
work more independently without having too much trouble maintaining a large codebase. Being able to update or
replace Frontend libraries in some parts of the application is yet another benefit in the fast-moving world of
frontend development.