From b221923e47a4c935ad17b00425e925316c423175 Mon Sep 17 00:00:00 2001 From: Florian Brandel Date: Thu, 8 Mar 2018 22:14:41 +0100 Subject: [PATCH] [TASK] Added micro-frontends to methods-and-patterns (assess) --- radar/2017-10-01/micro-frontends.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 radar/2017-10-01/micro-frontends.md diff --git a/radar/2017-10-01/micro-frontends.md b/radar/2017-10-01/micro-frontends.md new file mode 100644 index 0000000..e1159e8 --- /dev/null +++ b/radar/2017-10-01/micro-frontends.md @@ -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 are used 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 client- or server-side can be tricky as well as keeping the overall +User Experience consistent. + +Despite the challenges Micro Frontends help us developing large application across multiple teams. Developers can +work more independently without having too much trouble maintaining a large codebase. Being able to update oder +replace Frontend libraries in some parts of the application is yet another benefit in the fast moving world of +frontend development.