Dynatrace

MARCH 24, 2023

Docker Swarm First introduced in 2014 by Docker, Docker Swarm is an orchestration engine that popularized the use of containers with developers. Kubernetes Also developed in 2014 and often referred to as K8s, Kubernetes has emerged as a de facto standard for container orchestration, surpassing Docker Swarm and Apache Mesos in popularity.

Infrastructure 176

Infrastructure Open Source Operating System Cloud 176

Dynatrace

AUGUST 11, 2022

Cloud providers then manage physical hardware, virtual machines, and web server software management. The FaaS model of cloud computing debuted in 2014 with startups like hook.io. This code is then executed on remote servers in response to an event, such as users interacting with functional web elements.

Development 239

Development Serverless Best Practices Lambda 239

Brendan Gregg

MARCH 16, 2024

2014: Java in Flames Broken Java Stacks (2014) When I joined Netflix in 2014, I found Java's lack of frame pointer support broke all application stacks (pictured in my 2014 Surge talk on the right). Back-end servers. Google should be no surprise because they pioneered continuous profiling.)

Java 145

Java Cache Google Hardware 145

Dynatrace

MAY 31, 2021

Since Kubernetes emerged in 2014, it has become a popular solution for scaling, managing, and automating the deployments of containerized applications in distributed environments. This virtualization makes it possible to efficiently deploy and securely run a container independently of the hosting infrastructure. What is Kubernetes?

Virtualization 132

Virtualization DevOps Infrastructure Cloud 132

Brendan Gregg

FEBRUARY 28, 2023

My personal opinion is that I don't see a widespread need for more capacity given horizontal scaling and servers that can already exceed 1 Tbyte of DRAM; bandwidth is also helpful, but I'd be concerned about the increased latency for adding a hop to more memory.

Performance 110

Performance Latency Cache Virtualization 110

Brendan Gregg

JULY 4, 2021

I summarized these topics and more as a plenary conference talk, including my own predictions (as a senior performance engineer) for the future of computing performance, with a focus on back-end servers. This was a chance to talk about other things I've been working on, such as the present and future of hardware performance.

Performance 140

Performance Latency Hardware Storage 140

Brendan Gregg

FEBRUARY 28, 2023

My personal opinion is that I don't see a widespread need for more capacity given horizontal scaling and servers that can already exceed 1 Tbyte of DRAM; bandwidth is also helpful, but I'd be concerned about the increased latency for adding a hop to more memory.

Performance 52

Performance Latency Cache Virtualization 52