SRE vs. DevOps [Understanding Differences & Similarities]

Site Reliability Engineering (SRE) and DevOps share a goal of building a bridge between development and operations. We'll explore and compare both approaches. Wondering to yourself, which is better for your company, SRE or DevOps? Neither SRE or DevOps is “better,” exactly, since they’re similar yet different in a few key ways: SRE, or site reliability engineering, is a methodology developed by Google engineer Ben Treynor Sloss in 2003.


Make your Onboarding Experience Better with a Murder Mystery Game

Onboarding a new tool can be boring. Or stressful. Or both. When onboarding an incident response tool, it can be difficult to make sure that your team is getting the most from the experience. Do you opt for a run-of-the-mill meeting, or try to learn while in an incident? Neither option is ideal. That’s why Petal’s DevOps Engineer Michael Cole found a new way to get his team using Blameless for their incident response process.


Incident Management and Response: Myth Busting Edition

Site Reliability Engineering – or SRE – is what happens when you ask software engineers to design an operations function. That is how Google VP Ben Sloss described the background and definition of SRE. The idea of SRE originated at Google. Since its inception, more and more organizations are adopting tactics related to SRE to maintain their competitive edge in information technology’s rapidly evolving world.

Super-Charge Your Site Reliability Practices with Runbook Automation

To win in today’s digital age, organizations need to balance product reliability and feature delivery with dynamic business needs and legacy and multi-cloud environments. Automation, as a main SRE practice, scales product reliability practices by reducing tedious tasks related to production operations, freeing up engineers to work on innovation.

No, SRE Is Not the New DevOps - Unless It Is

If you start typing “DevOps vs.” in your search engine, you’ll probably see that “DevOps vs. SRE” is one of the top queries that people search for. But so are terms like “is SRE DevOps?” If Google autocomplete is to be believed, then, there is a fair amount of uncertainty out there about what, exactly, the SRE role has to do with DevOps. Some see SRE and DevOps as distinct concepts, while others apparently think that they mean more or less the same thing.


SRE Leaders Panel: Business Agility is what matters, SRE can help you get there

Blameless recently had the privilege of hosting SRE leaders Garima Bajpai, Founder at Community of Practice - DevOps Canada and Jason Fraser, Delivery Lead at VMware Tanzu to discuss the value of crisis during incident response, the best and worst tech transformations they’ve seen, how reliability impacts the flow of value, and more.


The Ultimate Guide to SRE Resources

It’s the year 2021, and Site Reliability Engineering (SRE) has become one of the fastest growing and hottest professions in the tech industry. With all of the attention on SRE, many software developers and operations engineers are now interested in moving into this burgeoning field. There is an enormous amount of information about SRE on the Internet – some helpful, some not so much. It can be hard to know where to begin.


SRE fundamentals 2021: SLIs vs. SLAs. vs SLOs

A big part of ensuring the availability of your applications is establishing and monitoring service-level metrics—something that our Site Reliability Engineering (SRE) team does every day here at Google Cloud. The end goal of our SRE principles is to improve services and in turn the user experience. The concept of SRE starts with the idea that metrics should be closely tied to business objectives. In addition to business-level SLAs, we also use SLOs and SLIs in SRE planning and practice.


4 Key Characteristics of Modern Monitoring

Our previous post, “Monitoring for Success: What All SREs Need to Know,” discusses how today’s complex IT environments — virtualization, cloud computing, continuous delivery and integration — coupled with pressures to deploy faster while meeting demands for “always on” customer expectations – have placed greater strains on monitoring teams.