Dynatrace

FEBRUARY 4, 2021

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.”

Engineering 259

Engineering DevOps Government Latency 259

Dynatrace

FEBRUARY 4, 2021

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.”

Engineering 184

Engineering DevOps Government Latency 184

Dotcom-Montior

OCTOBER 6, 2021

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.

Engineering 67

Engineering DevOps Monitoring Google 67

All Things Distributed

DECEMBER 20, 2017

That was the provocative thesis of a much-talked-about article from 2003 in the Harvard Business Review by the US publicist Nicolas Carr. The benefit for customers: Authorized users can view this data and therefore manage their inventories across different sites, making the maintenance processes much more efficient.

Artificial Intelligence 79

Artificial Intelligence Social Media Logistics AWS 79

The Symphonia

JANUARY 21, 2019

Back in the Dim And Distant Past of 2003 I even co-led an open source project that brought some at-the-time interesting innovations to this area. Think “GitHub Light”, useful if you want to keep your entire SDLC (Software Development LifeCycle) infrastructure in one AWS account. think EC2 services, staggered release, etc.

AWS 40

AWS Open Source Lambda Serverless 40

Tim Kadlec

JULY 31, 2013

And so it’s important to continually invest in stability, in strong infrastructure, in stable code, so that we have that strong platform to stand on as the next thing happens. Instead, to support a browser, we want to give the browser what it can handle, in the most efficient way possible. That was 2008.

Google 40

Google Website Hardware Games 40