
Anti-Patterns and Pitfalls

#47 - Micro-Frontends and the Socio-Technical Aspect - Luca Mezzalira
Topic 12 of 16
Published Jul 19, 2021 · Clip 36:22–40:44 (4:22)
Luca identifies key anti-patterns: a global state across micro-frontends creates design-time and organizational coupling, so he recommends keeping state inside micro-frontends and communicating via Pub/Sub patterns (event emitters, custom events, reactive streams)—analogous to choreography over orchestration in microservices. Multiple technologies in the same view is also an anti-pattern due to performance; teams should stick to one framework per boundary. He describes DAZN's strangler pattern migration, using canary releases and fast CI/CD to build developer confidence, moving from a few to tens of deployments per month.