A history of Site Reliability Engineering from its origins at Google in 2003 to the present.

Curious about DevOps benefits? Whether you are just adopting DevOps or improving your current process, we explain the top benefits and how to maximize them. What are DevOps benefits? In DevOps, the operations and development work closely together during the entire software development lifecycle. The collaborative approach in DevOps leads to many benefits, including.

One of the foundations of incident management in SRE practice is the incident retrospective. It documents all the learnings from an incident and serves as a checklist for follow-up actions. If we step back, there are 7 main elements to a retrospective. When done right, these elements help you better understand an incident, what it reveals about the system as a whole, and how to build lasting solutions.

In one of our previous articles, we discussed what an SRE is, what they do, and some of the common responsibilities that a typical SRE may have, like supporting operations, dealing with trouble tickets and incident response, and general system monitoring and observability. In this article, we will take a deeper dive into the various SRE principles and guidelines that a site reliability engineer practices in their role.

Follow these steps to write a great SRE job resume.

SRE is important and becoming more essential as software becomes a ubiquitous part of our life. Business leaders recognize this but fear they lack the resources to properly adopt SRE. Even large companies with mature DevOps functions experience headwinds.

Improving your influence over the company will help you deliver high quality work as your goals will be closely aligned with those of the company. In this blog piece, Ricardo has explained how to improve your influence as an SRE. Balancing fast-paced business requirements with the demands of keeping production services stable is not an easy task.

Curious about microservice architecture? We explain what microservice architecture is, and how it can be used to quickly produce reliable lightweight applications.

The need for relevant and contextual telemetry data to support online services has grown in the last decade as businesses undergo digital transformation. These data are typically the difference between proactively remediating application performance issues or costly service downtime. Distributed tracing is a key capability for improving application performance and reliability, as noted in SRE best practices.

An explanation of the meaning of SLA, SLO and SLI, and how SREs should use each concept to manage reliability.