article thumbnail

DevOps automation: From event-driven automation to answer-driven automation [with causal AI]

Dynatrace

The evolution of DevOps automation Since the concept of DevOps emerged around 2007 and 2008 in response to pain points with Agile development, DevOps automation has been continuously evolving. Consider an event-driven automation system designed for incident management.

DevOps 228
article thumbnail

Rebuilding Netflix Video Processing Pipeline with Microservices

The Netflix TechBlog

The Netflix video processing pipeline went live with the launch of our streaming service in 2007. When Reloaded was designed, we focused on a single use case: converting high-quality media files (also known as mezzanines) received from studios into compressed assets for Netflix streaming.

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

The Surprising Effectiveness of Non-Overlapping, Sensitivity-Based Performance Models

John McCalpin

The presentation discusses a family of simple performance models that I developed over the last 20 years — originally in support of processor and system design at SGI (1996-1999), IBM (1999-2005), and AMD (2006-2008), but more recently in support of system procurements at The Texas Advanced Computing Center (TACC) (2009-present).

article thumbnail

A Decade of Dynamo: Powering the next wave of high-performance, internet-scale applications

All Things Distributed

With these requirements in mind, and a willingness to question the status quo, a small group of distributed systems experts came together and designed a horizontally scalable distributed database that would scale out for both reads and writes to meet the long-term needs of our business. This was the genesis of the Amazon Dynamo database.

Internet 128
article thumbnail

The Ever Given is Not a Black Swan Event

The Agile Manager

The disruption is not simply the result of a ship running aground and blocking traffic in a busy, narrow passageway. I kept a copy of the October WSJ article intending to use it as a metaphor for large software development processes designed to optimize labor unit costs, specifically developer labor unit costs.

article thumbnail

The Best In Performance Interview Series – Episode #4: Recap with Rich Howard

Rigor

He goes into detail covering the steps that need to be taken to ensure that a website or application is prepared for an influx of traffic, from scoping and testing to setting expectations and creating a contingency plan. “There are a lot of different scenarios where you will be expecting more traffic than normal.”