Skip to content

Commit eb0e70e

Browse files
authored
Merge pull request neuland#15 from ewolff/patch-1
Fixed missing dash in Self-contained Systems
2 parents 9e8ef1c + 0bd40ff commit eb0e70e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The term __Micro Frontends__ first came up in [ThoughtWorks Technology Radar](ht
66

77
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 has a __distinct area of business__ or __mission__ it cares about and specialises in. A team is __cross functional__ and develops its features __end-to-end__, from database to user interface.
88

9-
However, this idea is not new, in the past it went by the name of [Frontend Integration for Verticalised Systems](https://dev.otto.de/2014/07/29/scaling-with-microservices-and-vertical-decomposition/) or [Self contained Systems](http://scs-architecture.org/). But Micro Frontends is clearly a more friendly and less bulky term.
9+
However, this idea is not new, in the past it went by the name of [Frontend Integration for Verticalised Systems](https://dev.otto.de/2014/07/29/scaling-with-microservices-and-vertical-decomposition/) or [Self-contained Systems](http://scs-architecture.org/). But Micro Frontends is clearly a more friendly and less bulky term.
1010

1111
__Monolithic Frontends__
1212
![Monolithic Frontends](./ressources/diagrams/organisational/monolith-frontback-microservices.png)

0 commit comments

Comments
 (0)