SREs and SWEs complement each other, but they perform different tasks and focus on different priorities.

Software development is getting faster and more complex – frustrating IT operations teams more than ever. So, DevOps gained popularity in order to combat siloed workflows, decreased collaboration and a lack of visibility. While establishing a culture of DevOps has helped teams collaborate better and deliver reliable software faster, DevOps teams don’t necessarily have someone specifically dedicated to developing systems that increase site reliability and performance.

Curious about DevOps CI/CD? We explain the continuous integration and continuous deployment pipeline and why it’s important to the DevOps process.

Developers around the world get their news from Changelog, an indie media company on a mission to create inspiring content for software developers. Through their popular podcasts, including The Changelog, Go Time, JS Party, and Ship It!, the team at Changelog helps listeners stay up-to-date on the latest happenings, trends, and tools in a constantly evolving industry.

One of the most challenging tasks for Site Reliability Engineers is to align the reliability of the systems with the business goals. There is a constant battle between delivering more features—which increases the product’s value—and keeping the system reliable and maintainable. A significant ally to achieve both objectives is the Service Level Objective Framework.

The evolution of Software Engineering over the last decade has lead to the emergence of numerous job roles. So how different is a Software Engineer, DevOps Engineer, Site Reliability Engineer and a Cloud Engineer from each other? In this blog, we drill down and compare the differences between these roles and their functions.

When learning SRE, you might find its principles a bit unintuitive. For example, it might be difficult to learn why aiming for 100% reliability is wasteful, or how reliability isn’t the same as availability, or why failure ought to be celebrated. Believe it or not, there is a method to these ideas. My goal in this article is to shed light on the principles and to leave you a believer, such that you’ll take steps towards starting SRE practices.

Learn about the key roles within an incident response team, as well as optional incident roles you may not have thought about.

The growing importance of technology in business success has forced practically all companies to hire competent, experienced IT professionals. As technology ecosystems become increasingly complex, organizations need a broader range of professionals to focus on tasks like product development, troubleshooting, and customer services. SRE and DevOps have emerged as two of the most critical approaches to success.

The role and responsibilities of a site reliability engineer (SRE) may vary depending on the size of the organization. For the most part, a site reliability engineer is focused on multiple tasks and projects at one time, so for most SREs, the various tools they use reflect their eve-evolving responsibilities. A typical SRE is busy automating, cleaning up code, upgrading servers, and continually monitoring dashboards for performance, etc., so they are going to see more tools in that toolbelt.

A couple of weeks back, Blameless attended SaaStr 2021, the go-to event for any business Go-to-Market (GTM) team which has been running since 2012. Our decision to sponsor was made in early 2020. Back then, we had no idea how long the pandemic would last or that it would be a full 18 months before we’d be able to do a physical event.

A lot of companies bequeath the projects that they build internally unto the world as open source. But they’re usually up for a pretty rude awakening when they ship their software and it has to be run for the first time by someone other than them.

A comparison of EKS, AKS, GKE, Rancher and OpenShift from an SRE’s perspective.

Catchpoint is proud to present the top SRE tools as voted on by SREs. In our fourth annual SRE Survey, compiled in partnership with VMware Tanzu Observability and DevOps Institute, we simply asked, “What are a few tools that every SRE should have available in their toolbelt?” Today, we are excited to share the findings with you. While some of the answers were not strictly tools, the analysis gives us valuable insight into the mindset of an SRE.

Facebook’s October 2021 outage was the type of event that gives SREs nightmares: A series of critical business apps crashed in minutes and remained unavailable for hours, disrupting more than 3.5 billion users around the world and costing about 60 million dollars. As incidents go, this was a pretty big one.

In a world with everything digital, you need AIOps to help ensure uptime and break through the noise. Still not sold? Let's explore 5 ways SRE and DevOps teams are using AIOps to boost existing monitoring tools.

A site reliability engineer, or SRE, is a role that that encompasses aspects of both software engineering and operations/infrastructure. It also encompasses a strategy and set of practices and principles across service offerings and is closely tied to DevOps and operations. The term site reliability engineering first came into existence at Google in 2003 when a site reliability team was created. At that time, the team was made up of software engineers.

xMatters is part technology, part service reliability, and a little bit of magic. If you’ve spent time on the xMatters website, you’ll likely have seen a number of valuable use cases for the platform—it can alert SREs when there’s a website outage, it can accelerate product development for DevOps teams, it can manage on-call schedules and alerts for support teams.

Looking into Incident Response? We explain incident response, the end-to-end process, the teams involved, and steps to take to avoid friction and slow-down. The goal is to manage the incident as efficiently as possible in order to restore or resume the service to its expected operational state.

The four key takeaways for SREs from Google’s State of DevOps 2021 report