7 Hard Lessons We Learned About Reliability Here at New Relic

New Relic has experienced significant growth and complexity over the past few years, handling over 30 million HTTP requests per minute, 600 million new data points, and 50 billion events queried daily. To address this growth, New Relic's reliability practices have undergone a major overhaul, with key lessons learned from high-severity incidents in 2014 and 2015. The company has implemented various measures to improve reliability, including manual processes being automated, defining realistic metrics of reliability, making the right answer easy every time, not waiting for perfect answers, and ensuring autonomy within teams while maintaining organizational support. Through these changes, New Relic aims to create a culture that prioritizes reliability in large-scale systems.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.