Schedule List ViewGrid View

Victoria Nguyen explains how Fastly overhauled the monitoring and data collection of its globally distributed network without its caches noticing.

Jamie Wilkinson offers a brief overview of SLOs, shares a practical guide to implementing sustainable SLO-based alerting for systems of any size, and outlines the tooling required to supplement the system in the absence of cause-based alerting.

Naoman Abbas offers an overview of tools Pinterest built to process trace data and the use cases they’ve enabled and shares some real-world examples. Join in to learn how to apply these techniques to your own challenges.

You're unsatisfied with one of your monitoring providers. You've considered finding a new solution, but the thought of migrating your data off their platform sounds extremely painful. Amy Nguyen and Cory Watson explain how to make a deadline for an infrastructure-critical software migration while ensuring that everyone's requirements are met and no data has been lost.

Three years ago, technical teams at USA TODAY NETWORK were completely siloed, making improvements and troubleshooting difficult and often blind to the rest of the technical organization. Bridget Lane and Kris Vincent explain how drastically the teams' tool belts, thought processes, and goals have changed as the company moved from silos to a single pane of glass.

Many companies adopt microservices to break down monoliths, but they soon uncover a hidden cost: How do you manage all these new interconnected things popping up? Michael Hamrah explains how to avoid creating Frankenstein's monster by understanding elements of a microservice platform. . .so you can sleep at night.

Containers can be a great infrastructure solution, but no one should drive them without a manual. Alice Goldfuss discusses some of the advantages and disadvantages of running containers in production at scale.

Jessica Frazelle explores some cool bits of Linux, including BPF and container technologies, and details new ways to trace various things in the kernel and how to even use these traces to hot patch kernels in the case of zero day vulnerabilities. Come for the jokes about Linux; stay for the live demos.

Jeffrey Valeo explains how to safely rollout complex changes at scale.

Idit Levine demonstrates common debugging techniques and offers an overview of Squash, a new tool and methodology that brings the power of modern popular debuggers to developers of microservices apps that run on container orchestration platforms.

Slack’s rapid growth over the last few years outpaced the original database’s scaling capacity, which negatively impacted the company's customers and engineers. Ameet Kotian explains how a small team of engineers embarked on a journey for the right database solution, which eventually led them to Vitess, an open source cluster database.

When building distributed applications, it's highly desirable to maintain a single source of truth, such as a database, for all application state. Unfortunately, for some applications, multiple sources of truth are unavoidable. Adam Wolfe Gordon shares strategies, learned from real-world experience, for managing multiple sources of truth without sacrificing consistency and usability.

Kristina Bennett shares best practices for practical data recoverability and shines a light onto some of the pitfalls awaiting the unwary, based on lessons learned from five years of data integrity tooling and consulting across Google.

Bart De Vylder shares his experience migrating an existing codebase and production environment to Kafka Streams, a relatively new and promising streaming library. Join in to see what aspects worked remarkably well and the challenges he ran into along the way.

Quantopian integrates financial data from vendors around the globe. As the scope of its operations outgrew cron, the company turned to Apache Airflow, a distributed scheduler and task executor. James Meickle explains how in less than six months, Quantopian was able to rearchitect brittle crontabs into resilient, recoverable pipelines defined in code to which anyone could contribute.

Implementing site reliability (SRE) engineering doesn't have to be intimidating, and it isn't only for cloud-native organizations. Liz Fong-Jones and Dave Rensin share eight key lessons Google's customer reliability engineering team learned helping large enterprises adopt SRE as an operations engineering model.

Matt Rogish explains how NTSB investigations of air disasters have dramatically improved flight safety and applies lessons learned in disaster recovery and analysis, teamwork, task saturation, and systems design to modern software application and infrastructure architecture at scale to achieve higher availability, reduced errors, and more scalable systems.

Waffle House's hurricane disaster plan has everything you could want from an IT disaster plan, including contact trees, failover states, and runbooks on partial operation. Heidi Waterhouse shares lessons about state drawn from the world outside computers and explains how to quantify them using a finite state machine and implement them automatically while you are in a less-than-perfect condition.

Effie Mouzeli explains why small-scale engineering is just as challenging as large-scale engineering and offers ideas on how to survive technical debt, poor communication, and other everyday challenges.

Rather than a future of NoOps, serverless has increased the need for specialized operations engineering. Jennifer Davis explores the role of operations in serverless, covering testing, monitoring, and debugging functions.

Christian Monaghan explains how he and his team successfully migrated HealthCare.gov, America's largest government website, to the cloud infrastructure provisioning tool Terraform, shares lessons learned along the way, and details how you can effectively use Terraform for your next project.

Finding the right balance between writing custom in-house software and using an off-the-shelf solution is difficult. Aish Raj Dahal sheds light on the age old build versus buy problem and "not invented here syndrome" by explaining how PagerDuty built a distributed task scheduler and later moved off it to use an off-the-shelf open source solution.

Good test coverage is essential for catching issues before a pull request has been merged, but they have to be the right kind of tests and must be reliable. Drawing on his experience at Microsoft, Sam Guckenheimer details what type of tests to do in your DevOps pipeline, when you should do them, and why.

Mike Newswanger explains how he used Kubernetes and Google Cloud to burst and extend the capacity of a physical infrastructure for optimizing almost 10 million images in less than two weeks.

Heather Osborn explains how Ticketmaster moved from a siloed on-premises environment to a DevOps hybrid cloud. If a company whose technology and human infrastructure have grown up organically around a custom-written VAX operating system can make the move to public cloud-native applications and begin a rapid march to a hybrid cloud solution, so can you.

Bots now make up over 50% of website traffic and have become the primary source of malicious application attacks, from DDoS to sophisticated intrusions. Laurent Gil lays out what you need to know about bot traffic, different types of bots, and real-world applications of ML and AI to identify and defeat malicious bots.

Automated anomaly detection in production using simple data science techniques enables you to more quickly identify an issue and reduce the time it takes to get customers out of an outage. Tuli Nivas shows how to apply simple statistics to change how performance data is viewed and how to easily and effectively identify issues in production.

API-based integration is fundamental to business strategy and continued success, but the explosion of APIs is creating incremental security risks that must be addressed. Laurent Gil explains why API security is quickly becoming a key cross-cutting concern for everyone from DevOps to the CISO.

Deepank Sharma offers an end-to-end look at continuous integration and continuous delivery (CI/CD), using Pipeline as Code and templates, quality gates, Docker, and Kubernetes while following best DevOps practices.

Cochairs Nikki McDonald, James Turnbull, and Ines Sombra welcome you to the first day of keynotes.

As our industry faces its biggest reckoning ever with the social, ethical and cultural impacts of technology, what can we learn if we reflect on the assumptions we build into our systems? How could our processes and tools be designed to undo the biggest bugs and biases of today’s tech?

Laurent Gil shares the latest cybersecurity research findings based on real-world security operations along with innovative approaches to managing and mitigating security events at the cloud edge.

The programmer's mind is inherently an activist's mind. Jessica McKellar draws parallels between the free and open source software movement and the work to end mass incarceration.

In critical path services such as DNS, stability is imperative above all else. Kris Beevers examines the trade-offs between risk and velocity faced by any high-growth, critical path technology business.

Machine learning has revolutionized many fields, from cancer detection to self-driving cars. And let's not forget about connected toilets that allow Alexa to flush at your command. Francesc Campoy Flores explores some of the techniques used and the most relevant research, focusing on use cases where machine learning can help developers be more efficient.

SRE has exploded in the industry over the last two years, with the publication of two best-selling books from Google. Not surprisingly, there have been questions about how SRE and DevOps relate. Do they compete? Do they reinforce each other? The short answer is that they make each other better. Join Dave Rensin to hear why.

Performance theory offers a rigorous and practical approach to performance tuning and capacity planning. Kavya Joshi dives into elegant results like Little’s law and the Universal Scalability Law. You'll also discover how performance theory is used in real systems at companies like Facebook and learn how to leverage it to prepare your systems for flux and scale.

Cochairs Nikki McDonald, James Turnbull, and Ines Sombra close the first day of keynotes.

Join us for the Sponsor Pavilion Reception on Tuesday, October 2, following the afternoon sessions.

Join other attendees during lunch at Velocity to share ideas, talk about the issues of the day, and maybe solve a few. Not sure which topic to pick? Don’t worry—it's not a long-term commitment. Try two or three and settle on a different topic tomorrow.

Join us for the social highlight of Velocity New York at one of New York's finest restaurants, Tao Uptown, located at 42 E 58th St. Enjoy great music, food, and cocktails while networking and making new connections.

Jumpstart your networking at Velocity at Speed Networking before the keynotes begin. Bring your business cards and prepare a minute of patter about yourself, your projects, and your interests.