Remove 2008 Remove Design Remove Latency Remove Traffic
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 217
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).

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

Zero Configuration Service Mesh with On-Demand Cluster Discovery

The Netflix TechBlog

A brief history of IPC at Netflix Netflix was early to the cloud, particularly for large-scale companies: we began the migration in 2008, and by 2010, Netflix streaming was fully run on AWS. Today we have a wealth of tools, both OSS and commercial, all designed for cloud-native environments.

Traffic 220
article thumbnail

Looking back at 10 years of compartmentalization at AWS

All Things Distributed

March 26, 2008 doesn't have any delicious desserts associated with it, but that's the day when we launched Availability Zones for Amazon EC2. Even though the network design for each data center is massively redundant, interruptions can still occur. This design has a double benefit.

AWS 132