#Microfrontends #LowConnectivity #AsianMarket
summary
Describes a microfrontend architecture that combines iframe isolation with npm-package deployments for versioning and distribution. Uses server-sent events (EventSource) instead of WebSockets to survive Chinese firewall conditions, applies a custom array-based serializer layered with gzip to reduce payloads about 3×, enforces contracts with TypeScript, and migrates the backend to a Fastify-based, Nest-like framework to achieve roughly 2× better performance.
AI-written summary · about
chapters (10)
- 0:00Microfrontends in Asian market
- 3:16Sports betting data flows
- 6:07Tech stack change
- 10:22Low connectivity in China
- 15:45EventSource vs WebSocket
- 17:54Microfrontend tech overview
- 19:23Master app architecture
- 22:31Bundle optimization
- 24:40Microfrontends vs monolith
- 25:24Summary & Q&A
related talks
47mMicro Frontends Unmasked
36mMicro Frontends in Action!
45mMicro Frontends in Action!
37mIntroduction to Micro Frontends
48mMicrofrontend Architecture – technical implementation.
31mMicro Frontends: The Good, the Bad, and the Ugly
34mMicro Frontends
30mMicro Frontends in React — a State of the Art Approach
