Coffee Chat
summary
Twenty-minute coffee-break panel that answers concrete micro‑frontend tradeoffs: whether to use an Angular/React shell or a lightweight vanilla shell, when Piral.Cloud or a framework makes routing and composition easier, and why a backend-for-frontend (BFF) often solves token distribution and API chattiness. Expect specific patterns for hybrid vertical/horizontal splits, advice on server-side vs client-side rendering at integration points, and recommendations on ownership, shared headers, and when to centralize components.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Shell routing challenges
- 3:59Hybrid microfrontend split
- 8:11Domain driven design limits
- 12:27Microfrontend with multiple services
- 15:38Header and footer separation
- 17:26Lunch break snack
- 18:29Common components across microfrontends
- 19:12Team domain separation
- 20:57Multi-tenancy microfrontends
- 22:23Feature-based ownership
- 23:49Raffle
related talks
01h 10mThe Future of Frontend Panel
27mMicro-Frontends Decisions Framework
46mMicro Frontend: the microservice puzzle extended to frontend
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends
46mA Round Table on The State of Front-End: (Ember, Angular, React)
21mEmbracing Micro-frontends: A Comprehensive Guide for Modern Web Development
51mMicrofrontends and UI Composition - a Code-First Dive
31mDecoupled, Not Disconnected: State and Sync in Micro-Frontends
