Lunch Panel
summary
Panel argues teams must prove that frontend decoupling actually reduces delivery time and operational pain rather than just being trendy, citing a CI/CD win framed as 50→3 minute CI/CD to show business impact. Technical specifics cover server rendering patterns with HTMX and React Server Components, runtime vs build-time composition (shell and microfrontends in one Docker image), isolation options (iframe, Shadow DOM, missing realm spec) and an import maps limitation that breaks native federation. Real-world references include large e‑commerce and high‑traffic sites like PayPal and Adidas and live sports platforms that scale to millions.
AI-written summary · about
chapters (6)
- 0:00Introduction and panel setup
- 1:08Convincing teams to adopt microservices
- 7:57Technical challenges in microservices
- 17:38API versioning and compatibility
- 23:18Large-scale microservices platforms
- 30:45Native web APIs and frameworks
related talks
41mPanel: Web
01h 10mThe Future of Frontend Panel
34mMicro Frontends
37mDemystifying Micro-Frontends
53mFuture of Frontend Panel
27mMicro Frontends: Break Up You Web App!
30mMicro Frontends in React — a State of the Art Approach
21mEmbracing Micro-frontends: A Comprehensive Guide for Modern Web Development