Schedule List ViewGrid View

Kris Nova tells the true and painful story of what it's like to move a monolithic enterprise app to running in a container in Kubernetes. Kris then prototypes a production environment that is designed to be as hard as possible to containerize and liberates the application into a scalable and modern cloud-native environment.

Michael Hausenblas walks you through troubleshooting applications running in Kubernetes, from application-level debugging to distributed tracing to chaos engineering.

Jason Yee shows how you can more easily test code in production while isolating the effect of potential issues using container orchestration and services meshes.

Neil Peterson leads a technical deep dive into using the Kubernetes Service Catalog to dynamically provision and consume managed cloud services.

The Financial Times recently migrated its content platform to Kubernetes. Join Sarah Wells to find out what it takes to migrate 150+ microservices from one container stack to another without affecting the existing production users and while the rest of your teams are working on delivering new functionality.

Technical interviewing is profoundly important, but unfortunately, it's easy to do poorly and very difficult to do well. Moishe Lettvin outlines strategies for reducing bias and increasing the fidelity of your technical interviews.

Ian Nowland challenges you to think broadly about the meaning of a "miss", and explains how a philosophy of owning and learning from them allows you to avoid more in the future. This enables you to grow as a manager, and so grow your impact on your organization.

Evolving teams and evolving companies are a constant in the career of a leader; helping your team navigate through that change becomes critical to your success as a manager and for the organization. Rocio Delgado shares dos and don'ts for managing and communicating change in your team or organization, which may highlight where your own skills need to evolve.

Accidental architecture is a product of circumstances rather than deliberate development toward a goal. James Thompson explains why it's best addressed by equipping teams to make more deliberate and informed technical decisions.

Sharon Steed explains what empathy is (and what it isn't) and gives you the tools you need to cultivate an empathy mindset at work and in life.

Preetha Appan outlines various failure modes ranging from network failures to entire server failures in Nomad, an open source scheduler that supports heterogeneous workloads.

Leemay Nassery discusses the importance of data collection pipelines and explains how to efficiently store datasets with the intention of making them easily accessible by a downstream machine learning platform.

Aviran Mordo discusses the challenges and real-life use cases of handling data in a distributed environment.

In the past five years, Alexander Rasmussen has spent a lot of time trying to get high-integrity data out of spreadsheets and into databases. Alexander explores common data integrity problems when dealing with spreadsheet data, investigates whether those integrity problems are inescapable, and shares ongoing work to mitigate them.

In 2007, Pat Helland published "Life Beyond Distributed Transactions: An Apostate’s Opinion," in which he conducts a thought experiment on how to design a distributed database that can scale almost infinitely. While the paper explicitly addresses distributed database design, Sean Allen shows that the ideas are far more widely applicable, particularly in scaling stateful applications.

Multiregion deployments can improve availability and latency and can cost way less than you think. Aaron Blohowiak dives into his experience operating in multiple regions at scale at Netflix and shares the algebraic models, code, and incident management playbooks the company has developed to tame, refine, and leverage its approach.

How do you refactor major, core functionality in a million-line codebase without disrupting the entire system? Maude Lemaire explains how Slack overhauled channels and shares the many obstacles the company overcame to boost both application performance and company-wide developer productivity (with only a few hiccups).

Now that adoption is ramped up and HTTP/2 is being regularly used on the internet, it's a good time to revisit the protocol and its deployment. Hooman Beheshti reviews protocol basics and digs into core features such as interaction with TCP, server push, priorities and dependencies, and HPACK.

Rewriting the key software component of your platform from scratch is always intimidating. Shannon Weyrick and James Royalty discuss NS1's recent DNS server rewrite and outline the steps the company took to roll it out across its globally distributed network with no downtime.

Join Casey Rosenthal to learn how to use chaos engineering to embrace complexity and navigate it rather than reject complexity and try to erase it.

Beyond looking out for a little green padlock in the browser bar, what do you need to know about secure connections as a programmer? What do people mean by terms like authentication, verifying a certificate, or signing a message? Join Liz Rice as she demystifies HTTPS, TLS, X.509, and more.

Seth Vargo outlines the key principles for securing microservices and distributed systems in the modern world, where applications run in cloud or hybrid cloud infrastructure.

Molly Crowther demonstrates how the enterprise can use cloud platforms to make security move at the pace of business—not the other way around.

Serverless shuffles security priorities, naturally mitigating certain risks while elevating others, as this live hacking session vividly demonstrates. Guy Podjarny breaks into a vulnerable demo serverless app while explaining each security mistake, its impact, and how it can be avoided. You'll leave knowing why you need to keep your functions secure and how to do it yourself.

Ian Coldwater offers practical advice about securing your Kubernetes clusters, from an attacker’s perspective.

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

Tammy Butow explains how your company can use Chaos Days to focus on controlled chaos engineering. Similar to Hack Days, Chaos Days encourage an open culture of engineering. However, instead of focusing on building features, Chaos Days help you focus on building more resilient systems and reducing incidents.

Scaling large systems and teams is hard. In the recent decade, we finally might have found a critical tool that causes us to believe this doesn't have to be the case. Jaana Dogan explains why Google teaches its tracing tools to "Nooglers" and how it helps them learn about Google-scale systems end to end without getting lost in the world’s largest systems company’s enormous code base.

Using aggregate analysis of O'Reilly Safari usage and search data, Roger Magoulas shares key insights and trends that are impacting the open source tools ecosystem—trends you can use to help make decisions that affect your next project, your organization’s strategic direction, and your own career.

For many open source developers, marketing can seem like a scam—pushing terrible software from one side of the mouth while ruining good software with the other. Michael Bernstein offers an unflinching look at some of the fallacies that developers believe about marketing.

Laura Thomson shares Mozilla's approach to data ethics, review, and stewardship, including practical open source guidelines for lean data and examples of when the company has gotten it right (and wrong).

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

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.

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.