...
Demo of single-spa with Adam Stankiewicz!
Arch Tea with Luca Mezzalira debrief
Notes/questions from that meeting: Arch Tea with Luca Mezzalira (Pre-Work) - 2020-07-09
SummaryTakeaways
Do these feel like the right take-aways?
Concerns MFE requirements DAZN doesn't have:
Many Domains (primarily a video tool - their whole business is 5 total)
Theming
Pluggability
Approachability
ability for new teams/community members to bootstrap/onboard/understand our code and build things that fit into the ecosystem
MFE principles at DAZN
No cross-MFE component sharing
No cross-MFE shared assets (runtime)
1 team, 1 MFE
Independent build systems, container-based
Spinner displayed on page load to give immediate feedback
Questions
How do these might the requirements above change our MFE strategy? From DAZN’s? From our current state?
How do DAZN’s principles compare to our needs?
Luca mentioned dividing MFEs by “user journey” through a DDD lens… Should we do the same at edX? How can we be better about doing so?
What steps can we take to improve our MFEs?