Remove 2003 Remove Latency Remove Software Remove Systems
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

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. Maintaining layouts became a particular pain point for static sites.

Ecommerce 139
article thumbnail

HammerDB Best Practice for PostgreSQL Performance and Scalability

HammerDB

This post gives a HOWTO guide on system configuration for achieving top levels of performance with the HammerDB PostgreSQL TPC-C test. Firstly for system choice a 2 socket system is optimal for PostgreSQL OLTP performance at the time of writing. CPUs which need to have their frequency coordinated by software: 0.

article thumbnail

HammerDB MySQL and MariaDB Best Practice for Performance and Scalability

HammerDB

As with the previous guides as an Intel employee (#IAMINTEL) the examples are taken from a MySQL 8 on Linux on Intel system and the approach is the same for whatever system you are testing although some of the settings you see may be different. System Setup: CPU, Memory and I/O Configuration. hardware limits: 1000 MHz - 3.80

article thumbnail

Transforming enterprise integration with reactive streams

O'Reilly Software

Build a more scalable, composable, and functional architecture for interconnecting systems and applications. Software today is not typically a single program—something that is executed by an operator or user, producing a result to that person—but rather a service : something that runs for the benefit of its consumers, a provider of value.