Avoiding software fails: few metrics to improve application reliability
summary
Focuses on concrete failure modes and measurable fixes: browser pages with 434 resources 20 MB that kill mobile loads, database storms with 25,000 DB calls per request and repeated SQL executed 12,000 times, connection setup taking nearly a minute, and debug logging that drops a 6‑minute response to about 1 minute when disabled. Recommends using F12, PageSpeed, WebPageTest, SQL profiler, count API calls, tune connection pools and reduce resource counts before trusting deployment.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:50Software reliability failures
- 5:42Testing in production
- 7:10Avoiding software fails
- 10:24Browser tools and optimization
- 11:08Architecture pitfalls
- 12:59Database inefficiencies
- 16:44Logging and exceptions
- 19:55Deployment differences
- 23:12Testing before release
- 23:56Connection pool sizing
- 27:08Key reliability metrics
- 28:13Resources and closing
related talks
29mClient Says Your Awesome Web App Works Slowly. Now What?
58mNeed for speed 8, performance tuning of your web application
48mPerformance Mistakes
53mPerformance Checklist for the Mobile Web
39mGiving you ways to increase, but also explain site performance, to your boss.
40m“Performance by Design”
41mHigh Performance Kick-Ass Web Apps
45mBuilding Web Apps That Don’t Suck