article thumbnail

Site reliability engineering: 5 things you need to know

Dynatrace

Site reliability engineering (SRE) is the practice of applying software engineering principles to operations and infrastructure processes to help organizations create highly reliable and scalable software systems. ” According to Google, “SRE is what you get when you treat operations as a software problem.”

article thumbnail

Site reliability engineering: 5 things to you need to know

Dynatrace

Site reliability engineering (SRE) is the practice of applying software engineering principles to operations and infrastructure processes to help organizations create highly reliable and scalable software systems. ” According to Google, “SRE is what you get when you treat operations as a software problem.”

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

What is a Site Reliability Engineer (SRE)?

Dotcom-Montior

A site reliability engineer, or SRE, is a role that that encompasses aspects of both software engineering and operations/infrastructure. 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.

article thumbnail

End of term

The Morning Paper

My end of term tradition is to highlight a few of the papers from the term that I especially enjoyed, but this time around I want to let one work stand alone: Making reliable distributed systems in the presence of software errors , Joe Armstrong, December 2003.

article thumbnail

HammerDB: Using MySQL 5.7 vs 8.0 to understand performance profiles

HammerDB

When a system ‘scales’ it is able to deliver higher levels of performance proportional to the system resources available to it. In particular, this means as we add CPU cores and increase the system load, we see higher performance. software running on the same server. and MySQL 8.0.25 and MySQL 5.7.33.

article thumbnail

Jamstack CMS: The Past, The Present and The Future

Smashing Magazine

During the 90s, we saw two content management systems for static sites — Microsoft FrontPage in 1996 and Macromedia Dreamweaver in 1997. These desktop applications incremented the tooling an inch closer to the modern Jamstack content management systems of today. Drupal has a rich and extendable permission system.

Ecommerce 139
article thumbnail

The Back-to-Basics Readings of 2012 - All Things Distributed

All Things Distributed

Werner Vogels weblog on building scalable and robust distributed systems. I am pretty sure some if not all of these papers deserved to be elected to the hall of fame of best papers in distributed systems. Feb 11 - A Survey of Rollback-Recovery Protocols in Message-Passing Systems , E. All Things Distributed. Comments ().