Managing Performance in a Hybrid SPA
summary
Freshservice moves from Rails SSR to an Ember hybrid SPA and uses a custom X-account-data-version header, service workers, memcache-backed backend caching keyed by locale agent and resource version, plus weak and strong ETags. At ~150k RPM the stack reduces CPU and network load and more than 50%+ 304 responses after rollout. Live resyncs trigger only changed APIs (fields return 200, others 304) so UI updates immediately without full recompute.
AI-written summary · about
chapters (9)
- 0:00Introduction to hybrid SPAs
- 1:50Why switch to Ember
- 3:58UX and accessibility benefits
- 5:43Data versioning header
- 7:10Service workers for caching
- 8:13Caching API responses
- 9:58Using ETags for performance
- 12:49Integrating all techniques
- 16:41Summary and conclusion
related talks
45mSPA, isomorphic and back to the server: our journey with JS
36mMake It Fast
33mSpeeding Up Your Front-End: 2016 Version
55mTechnology agnostic microservices at SPA frontend
25mSpeed at Scale: Optimizing The Largest CX Platform Out There
01h 06mA High-Performance Solution to Microservices UI Composition
30mBringing it all together
17mSpeed at Scale: Optimizing The Largest CX Platform Out There