Keynote: Best Practices – UI, API and Server-side
summary
Cazton delivers a case study: five developers build 40 of 108 web components in one month and ship a fast, secure multi-device app. Key claims: server responses target ~50 ms, memoization cuts a recursive JavaScript call from ~331 million invocations to 39, and critical UI is server‑rendered with inline CSS for fast interactivity. Architecture uses search DB for queries, document DB for product specs, RDBMS only for orders, plus Redis/Memcache for shared caching and avoid repeated reflows/paints.
AI-written summary · about
chapters (21)
- 0:00Start
- 1:0914 Rules of Web Performance
- 2:55Critical Rendering Path
- 6:32async
- 9:46Older Browsers
- 10:23Gmail Mobile
- 12:08Performance (60fps)
- 12:50Layout Update
- 14:17Layout To Paint
- 18:44Reducing Reflow Impact
- 21:53Brewer's CAP Theorem
- 22:56Why is Scalability Important?
- 24:27Vertical Scaling
- 26:43Vertical Partitioning (Services)
- 29:02Microservices
- 31:07Caching
- 31:59Vertical Partitioning (Hardware)
- 32:45Vertical Partitioning (DB)
- 35:12Scalable solution
- 46:58Error Format
- 47:42Versioning
related talks
51mBuilding Amazing Single Page Applications the Right Way
18mThe need for speed - Single-page apps, Optimistic UIs, Reactivity
20mKeynote: JavaScript: Enterprise Adoption and Usage
21mHow not to end up your app to a hot mess of spaghetti Carbonara
30mPanel Discussion: Winning Web and Native Apps
42mChallenges for Developers of Building Large Web Applications
30mBringing it all together
23mShares Top Tips for Building Supercharged Web Applications Today!