Remove 2003 Remove Google Remove Latency
article thumbnail

Site reliability engineering: 5 things you need to know

Dynatrace

As a discipline, SRE focuses on improving software system reliability across key categories including availability, performance, latency, efficiency, capacity, and incident response. ” 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

As a discipline, SRE focuses on improving software system reliability across key categories including availability, performance, latency, efficiency, capacity, and incident response. ” 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.

article thumbnail

Fast key-value stores: an idea whose time has come and gone

The Morning Paper

In ProtoCache (a component of a widely used Google application), 27% of its latency when using a traditional S+RInK design came from marshalling/un-marshalling. The network latency of fetching data over the network, even considering fast data center networks. What have the authors got against this combination? Who knew! ;).

Cache 79
article thumbnail

What is a Site Reliability Engineer (SRE)?

Dotcom-Montior

The term site reliability engineering first came into existence at Google in 2003 when a site reliability team was created. The term “Site Reliability Engineer” is attributed to Ben Treynor Sloss, now a Vice President of Engineering at Google. At that time, the team was made up of software engineers.

article thumbnail

Supercomputing Predictions: Custom CPUs, CXL3.0, and Petalith Architectures

Adrian Cockcroft

There is a trend in the industry where Apple, Amazon, Google and others are now designing their own CPUs and GPUs, and NVIDIA has added the ARM based Grace CPU to its Hopper GPU in its latest generation. I presented a keynote for Sun at Supercomputing 2003 in Phoenix Arizona and included the slide shown below.

article thumbnail

Transforming enterprise integration with reactive streams

O'Reilly Software

In 2003, Gregor Hohpe and Bobby Woolf released their book Enterprise Integration Patterns. AWS, Kafka, Google Cloud, Spring, ElasticSearch). Orchestration tooling was also not ready for SOA, with manual deployment scripts being one of the most common ways of deploying new versions. The rise of enterprise integration patterns.

article thumbnail

WebPageTest API

CSS - Tricks

google-analytics.com", "sanList":[ "*.google-analytics.com", google-analytics.com", "*.fps.goog", Linux; Android 6.0.1; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.85 Mobile Safari/537.36 PTST/210419.211328", "accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9",