Reliability Engineering: History, Practice, and Future

https://is1-ssl.mzstatic.com/image/thumb/Podcasts211/v4/67/c8/43/67c8430f-7e3e-bcba-4469-54787206cb90/mza_12433984773424099588.jpg/600x600bb.jpg

Code Impact

Sanket Makhija

72 episodes

4 days ago

Welcome to "Code Impact," the podcast where we explore code that has an impact. Each episode dives deep into real-world stories, practical case studies, and expert insights, showcasing the powerful impact of code on performance, accessibility, and user experience. Whether you're a seasoned developer or just starting your journey, "Code Impact" delivers the tools, tips, and inspiration you need to create meaningful and high-performing products. Join us as we uncover the ways coding is transforming industries and making a difference—one line at a time. NotebookLM creates all episodes.

Education

RSS

All content for Code Impact is the property of Sanket Makhija and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Education

https://d3t3ozftmdmh3i.cloudfront.net/staging/podcast_uploaded_nologo/42227160/42227160-1728916697741-cd37329d2cc32.jpg

Reliability Engineering: History, Practice, and Future

Code Impact

13 minutes 50 seconds

9 months ago

Reliability Engineering: History, Practice, and Future

This podcast explores the field of reliability engineering, tracing its origins at Google with the development of Site Reliability Engineering (SRE). It differentiates reliability engineering from SRE, highlighting its broader applicability across various organisational structures. The podcast outlines four key promises of a successful reliability team: defining service levels (SLA/SLO/SLI), managing the service infrastructure, participating in technical design, and providing tactical support during incidents. Finally, it discusses the evolving landscape of reliability engineering, emphasising pragmatic approaches to balancing cost and reliability needs, and advocating for a more nuanced understanding of when to build versus buy solutions.