Continuous Performance
summary
Conference claims show 17% deploy daily and argues continuous performance needs three concrete things: monitor business KPIs alongside front-end and back-end metrics, log every change/event so each deployment is a measurable milestone, and pair dashboards/alerts with analytics for before-after analysis. Example ecommerce incident finds a missing database index that raises page load times and drops conversion until the index is added and revenue recovers, proving monitoring ties deployments to measurable business impact.
AI-written summary · about
chapters (5)
related talks
31mThe Continuous Delivery Paradox - Balancing Business Value with Speed
26mThe Many Ways to Deploy Continuously
44mContinuous Performance Testing in DevOps
41mPerformance Engineering in the Age of DevOps and Agile
23mContinuous Deployment - The Last Frontier for Continuous Delivery
33mContinuous Delivery - What does good really look like?
31mFireside Chat: Continuous Deployment
36mWhat do we know about continuous delivery – and what would we like to know
