Architecture for an ever changing environment” by Zendesk (Main Stage)
summary
Zendesk Copenhagen splits a large SPA into independently deployed pieces using a micro-frontend architecture served by a mono-repo with top-level server that routes to each app’s index.html. Development uses per-app webpack dev servers proxied by the top server, and yarn workspaces with linked dependencies let teams use different frameworks while a CI tool computes git hashes to only rebuild affected apps. Trade-offs include full page reloads, careful caching, and faking the chrome for fast perceived loads.
AI-written summary · about
chapters (12)
- 0:00Zendesk introduction
- 1:17Zendesk ticketing and CMS
- 3:50Change in large apps
- 5:18Monolith risks and complexity
- 9:20Modular architecture
- 13:31Modularization benefits
- 16:23Technology transitions with modularity
- 17:49Shared component library
- 19:56Managing libraries and dependencies
- 23:02Full page reloads in modular apps
- 24:51Performance and UX optimization
- 27:04Conclusion and key takeaways
related talks
24mScaling Frontend Development using Micro-frontends
57mMicro Frontends – a strive for fully verticalized systems
36mMicro Frontends - Breaking Monoliths
19mHarnessing Microfrontends: Platforms for Web Apps
21mMicro-frontends: 3 years ago
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
13mMicro Frontends Without Chaos: Architecture That Survives Scale
22mMicro Frontends & me, a love story