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

Merge pull request #22 from AOEpeople/radar-2021-01-01-page-composing

Browse Source 
Page composing
This commit is contained in:
bmsuseluda
2021-06-02 13:29:28 +02:00
committed by GitHub
parent 76a91fcb89 a4954e87c2
commit 104bfd5438
3 changed files with 23 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2018-03-01/micro-frontends.md
View File

@@ -12,6 +12,6 @@ challenges. Integrating different Frontends on the client- or server-side can be
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 oder
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.

9
radar/2021-01-01/micro-frontends.md Normal file
View File

@@ -0,0 +1,9 @@
---
title: "Micro Frontends"
ring: adopt
quadrant: methods-and-patterns
---
The Micro Frontends approach continues to prove to be a valuable pattern for large-scale systems developed by several teams. Therefore, we moved this pattern to "adopt".
We use [page composing](methods-and-patterns/page-composing.html) as one implementation of this pattern.

13
radar/2021-01-01/page-composing.md Normal file
View File

@@ -0,0 +1,13 @@
---
title: "Page Composing"
ring: trial
quadrant: methods-and-patterns
---
Page composing is a way to aggregate multiple independent page fragments into one combined web page. As an implementation of [Micro Frontends](methods-and-patterns/micro-frontends.html), this approach supports to deploy and run services agnostic to the technologies used per team.
The concept builds upon the fact that all involved services deliver valid HTML as their output. Our solution is a small application which takes care of gathering the page fragments from all services and composing each into a defined HTML template. A configuration layer further allows to control which fragment gets pulled from the serving instance.
With such a page composing application in place, teams can autonomously develop, deploy and operate their service with the freedom of choosing technologies and release strategies.
Martin Fowler et al. described this as [Server-side template composition](https://martinfowler.com/articles/micro-frontends.html#Server-sideTemplateComposition).