Remove Google Remove Handbook Remove Infrastructure Remove Processing
article thumbnail

Site reliability done right: 5 SRE best practices that deliver on business objectives

Dynatrace

How site reliability engineering affects organizations’ bottom line SRE applies the disciplines of software engineering to infrastructure management, both on-premises and in the cloud. There are now many more applications, tools, and infrastructure variables that impact an application’s performance and availability.

article thumbnail

Implementing service-level objectives to improve software quality

Dynatrace

When organizations implement SLOs, they can improve software development processes and application performance. SLOs can be a great way for DevOps and infrastructure teams to use data and performance expectations to make decisions, such as whether to release and where engineers should focus their time. SLOs improve software quality.

Software 259
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

9 key DevOps metrics for success

Dynatrace

While DevOps is often referred to as “agile operations,” the widely quoted definition from Jez Humble, co-author of The DevOps Handbook, calls it “a cross-disciplinary community of practice dedicated to the study of building, evolving, and operating rapidly-changing resilient systems at scale.” Change failure rate.

DevOps 196
article thumbnail

Tutorial: Guide to automated SRE-driven performance engineering

Dynatrace

While Google’s SRE Handbook mostly focuses on the production use case for SLIs/SLOs, Keptn is “Shifting-Left” this approach and using SLIs/SLOs to enforce Quality Gates as part of your progressive delivery process. This will enable deep monitoring of those Java,NET, Node, processes as well as your web servers.

article thumbnail

2017 Wheel of Fortune

J. Paul Reed

The DevOps Handbook was published last year, and I think that will put the question to eternal rest. Even though there are numerous other books (and opinions, for that matter) on the subject, I believe The DevOps Handbook will become the de facto arbiter of what officially is and is not “DevOps.” And we now have that.

DevOps 40
article thumbnail

Smashing Podcast Episode 42 With Jeff Smith: What Is DevOps?

Smashing Magazine

But more about processes and ways of communicating on workflows, is that right? So my mantra for the last 20 years has always been people process tools. From there, you define whatever your process is going to look like to achieve that vision. And then you bring on tools that are going to model whatever your process is.

DevOps 83