SPA at Scale
summary
A large internal SPA called Beehive totals 200,000 lines of code and supports over 50 front end engineers across Seattle San Francisco Cupertino and Vancouver so scalability problems are concrete not hypothetical. Cross browser and OS edge cases break virtual lists and performance on corporate Firefox builds so teams adopt tooling like TypeScript for self documenting interfaces, Jest and enzyme for unit and snapshot tests, webpagetest and Lighthouse for network simulation and CloudWatch for production monitoring and alerts while prioritizing small atomic changes and empathy when reviewing code.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:44Single Page Applications at Scale
- 1:20Top Five Lessons Learned So Far
- 2:35Operating System Issues
- 4:50Documentation Documenting Our Code
- 6:13Distributed Teams
- 9:18Testing Framework
- 10:52Monitors and Alarms
- 11:48Lesson for Yakhni
related talks
25mLessons for frontend development at scale
34mHow to build front-end web apps that scale
43mRethinking SPAs: web-native apps
26mBeyond the Hype: Facing Micro Frontend Challenges in Large Scale
15mEstablishing Platform Teams to Utilize the Economy of Scale
28mArchitecture for an ever changing environment” by Zendesk (Main Stage)
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
24mScaling Frontend Development using Micro-frontends