@duο¬eit
We were so committed to the concept
of Micro Frontends that we began
addressing all the technical challenges
associated with their implementation.
@duο¬eit
Build Time
Browser
π·
π
Mono repos
Compose MicroFrontend
Build Time
Integration
Slide 14
Slide 14 text
@duο¬eit
Server Side
Browser
π·
π
SSI
Compose MicroFrontend
π· π· π·
π¦ π¦ π¦ π¦
ESI
Independent
Deployments
Resilience
Server Side
Integration
@duο¬eit
Browser
Slow Rendering
Times
Slow Rendering Time
β³ β³ β³ β³
Slide 22
Slide 22 text
@duο¬eit
Progressive enhancement
Slide 23
Slide 23 text
@duο¬eit
SSR
Slow Rendering Time
Browser
Hydration
π
π
Slide 24
Slide 24 text
@duο¬eit
Frontend Communication
Browser
Slide 25
Slide 25 text
@duο¬eit
Frontend Communication
Browser
Slide 26
Slide 26 text
@duο¬eit
Frontend Communication
Browser
Slide 27
Slide 27 text
@duο¬eit
Frontend Communication
Browser
π π π π
Contract Libs
Backward or Forward
compatible to avoid
Breaking Changes
Slide 28
Slide 28 text
@duο¬eit
πͺ’ Integration Patterns
β» Reusage of Global Dependency
π¦ SSR and Hydration
β Client Side Integration
And many more
Slide 29
Slide 29 text
@duο¬eit
Micro Frontends are a technical
challenge with is basically solved.
Slide 30
Slide 30 text
@duο¬eit
Micro Frontends are a technical
challenge with is basically solved.*
*famous last words
Slide 31
Slide 31 text
@duο¬eit
How big should a Micro Frontend be?
Which is not a technical Question.
Only as big to still ο¬t
in our heads as a team.
Daniel Terhorst-North
@duο¬eit
Typically, we do not achieve full
end-to-end verticalization in our value
streams.
As it is usually not beneficial to divide our value
streams based solely on the provided UI representation.
@duο¬eit
Much of our complexity has started to
reside outside of the value streams and
instead lies in the orchestration of
these ο¬nely-grained Micro Frontends.
Which ultimately introduces high coupling.
Independent
Deployments
Resilience
@duο¬eit
Product Search
π§ π§
π§
π
Product
Catalogue
Rating
Basket
π§ π§
π§
π§ π§
π§
π§ π§
π§
The integration and orchestration of
the various capabilities oο¬ered by the
value streams do not occur "between
the teamsβ.
One team accountable for delivering a
great customer experience.
@duο¬eit
So many thing to consider,
Letβs sum up.
Slide 52
Slide 52 text
@duο¬eit
We possess most of the technical foundations
necessary to successfully build Micro Frontends.
Slide 53
Slide 53 text
@duο¬eit
But Micro Frontends do not address technical
challenges, they serve as a means to scale our
engineering organization through
full end-to-end verticals.
Slide 54
Slide 54 text
@duο¬eit
π§ π§
π§
π§ π§
π§ π§ π§
π§
Autonomous
Teams
USER
π
Useful vertical slices
frequently do not align
with the expected
frontend channel
experience.
π§ π§
π§
Slide 55
Slide 55 text
@duο¬eit
Micro Frontends address the sociotechnical
challenge of enabling fully end-to-end
verticalized organizations, a situation we rarely
encounter in practice.
Slide 56
Slide 56 text
@duο¬eit
π§ π§
π§
π§ π§
π§ π§ π§
π§
π§ π§
π§
Autonomous
Teams
USER
π
π§ π§
π§
Slide 57
Slide 57 text
@duο¬eit
The more your value streams diο¬er from your
user ο¬ows, the less Micro Frontends are the
answer.
Slide 58
Slide 58 text
@duο¬eit
DAVID LEITNER
Coding Architect
π [email protected]
π @duο¬eit