Schedule

Charles Pretzer explains how to deploy a service mesh in production from the ground up using Linkerd. You'll briefly review the fundamentals of microservice architectures and concepts, then dive into hands-on exercises on deploying an application and using Linkerd to collect metrics and shape traffic.

James Gough, Padma Sridhar, and Matthew Auburn walk you through the creation of a very simple task list API.

Join Scott Davis to explore W3C specifications like the Web Speech API (for speech synthesis and speech recognition), Speech Synthesis Markup Language (SSML), and WebVTT (for closed captioning). These technologies not only power smart speakers from Amazon, Google, Microsoft, and Apple; they power smartphones and desktop browsers as well.

Debugging distributed systems is hard, especially with abstractions and automated orchestration at every layer. Christian Posta explains how to find and resolve application- and environment-level issues using Envoy Proxy and open source projects Gloo Shot and Squash to experiment with and debug applications without affecting production traffic.

Mike Amundsen explains the important balance between designing, building, and releasing APIs. You'll learn how to create a consistent process for your company to ensure your API teams produce quality APIs that developers can easily use to provide timely business solutions for your organization.

If you've ever struggled with a microservices architecture or read about event sourcing and CQRS but were disappointed to only find high-level descriptions, this course is for you. Ethan Garofolo helps you get hands-on and actually learn these concepts as you discover how to model state as events and build the pieces of a fully functioning system.

Event-driven design (EDD) scales from small, simple applications to large, complex systems, and it provides the ability to extend applications with new functionality and retroactively catch up on historical domain events. Sasha Jolich explains how to create a to-do web app using EDD.

Upfront architecture is essential to ensure reliability. Ideally, the system design starts with defining clear service-level objectives (SLOs) that translate into the right architecture to avoid gold-plating or costly redesigns after the system is live. Marco van der Linden and Tom Hofte explain how to define clear SLOs and apply architectural patterns to design a system that works as promised.

Join a group of fellow attendees for dinner at one of New York's great restaurants. This event is not sponsored, so you're responsible for paying your portion of the bill.