Architecting for Change at Scale

Regardless of industry, programming language, or company size, change is a necessity in technology. We can’t effectively anticipate all future evolutions, but we can learn from past experiences to inform how to make our systems easier to change without over-engineering. The ability to safely and effectively deploy change at scale can be the difference in beating competitors to market, mitigating zero-day vulnerabilities, keeping developers happy, and ensuring customers have a reliable product.

Change is present every day in how we evolve our systems and release features. It is there when we decide to adopt a new technology or migrate systems from one solution to another. It’s also there when we need to rapidly address large-scale vulnerabilities at scale like we saw last year with log4j.

In this track, attendees will learn patterns and practices to help them architect systems and tooling with agility top of mind – enabling technology to keep up with the needs of the business while minimizing risk and technical debt

From this track

Session Architecture

Adopting Continuous Delivery at Lyft

Thursday Dec 1 / 09:00AM PST

All organizations, regardless of size, need to be able to make rapid changes and improvements in their constantly growing systems. How can we handle all this change while maintaining a reliable product? 

Speaker image - Tom Wanielista

Tom Wanielista

Senior Staff Software Engineer @Lyft

Session Architecture

Dark Side of DevOps

Thursday Dec 1 / 10:10AM PST

Topics like “you build it, you run it” and “shifting testing/security/data governance left” are popular: moving things to the earlier stages of software development, empowering engineers, shifting control definitely sounds good.

Speaker image - Mykyta Protsenko

Mykyta Protsenko

Senior Software Engineer @Netflix

Session Architecture

Stress Free Change Validation at Netflix

Thursday Dec 1 / 11:20AM PST

How do you gain confidence that a system modification does what it’s supposed to do? A refactoring should not cause a functional change, whereas a feature modification should cause a specific kind of change.

Speaker image - Javier Fernandez-Ivern

Javier Fernandez-Ivern

Senior Software Engineer @Netflix

Session Architecture

Log4Shell Response Patterns & Learnings From Them

Thursday Dec 1 / 12:30PM PST

In early December 2021, rumors about a remote code execution (RCE) vulnerability in Log4j began circulating on social media, dubbed Log4Shell. Over the next three days, those rumors were confirmed and the immense scope of the vulnerability became clear.

Speaker image - Tapabrata Pal

Tapabrata Pal

Vice President of Architecture @Fidelity

Date

Thursday Dec 1 / 09:00AM PST

Share

Share Share

Track Host

Haley Tucker

Senior Software Engineer for Productivity Engineering @Netflix

Haley Tucker is a Senior Software Engineer for Productivity Engineering at Netflix where she is responsible for building systems and tools which reduce friction in the Software Development Lifecycle (SDLC), allowing developers to focus more on their business goals. Prior to that, she was a member of the Resilience Engineering team responsible for improving the reliability of the Netflix ecosystem through trustable and safe tooling. She has also worked on the Playback Features team where her services filled a key role in enabling Netflix to stream content to millions of members on thousands of device types worldwide. Prior to Netflix, Haley spent a few years building custom billing and payment solutions for cloud and telephony service providers as a consultant as well as near-real-time command and control systems at Raytheon. Haley enjoys applying new technologies to develop robust and maintainable systems, and the scale at Netflix has been a unique and exciting challenge. Haley received a BS in Computer Science from Texas A&M University

Read more
Find Haley Tucker at: