Lee Atchison (New Relic)
summary
Argues that scaling failures usually come from a tiny piece of logic whose complexity explodes and causes repeated outages (examples include recurring ~20-minute downtimes), and prescribes concrete actions: build a risk matrix to rank what truly threatens availability, focus remediation on highest-impact technical debt rather than obvious chores, and increase organizational visibility using New Relic-style APM so owners of microservice-based architectures can see how their component affects the whole.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:07What Do You Do at New Relic
- 0:25Architecting for Scale
- 4:05Fill Out a Risk Matrix
- 6:24What Do You Think Are the Most Important Factors That New Relic Will Be Bringing to Your Partners in the in the Next 12 Months
related talks
31mEvolving performance assurance
05mScale Fail
34mToward continuous resilience
44mIntroduction to application scaling
17mContinuous resilience: Managing your application risks
13mBeyond observability: Using reliability scores to drive results
26mBeat the curve how to stay fast at scale
41mPerformance Engineering in the Age of DevOps and Agile