Engineering the Future of Software
Feb 25–26, 2018: Training
Feb 26–28, 2018: Tutorials & Conference
New York, NY

Schedule: Devops sessions

The advent of DevOps has permanently changed what a developer or architect is responsible for and can impact in the lifetime of a software system. Long gone is the idea of building a project and throwing it over the wall at the operations team. Now it is all about continuous integration, how best to use the cloud, version control on GitHub, and testing from the beginning. And to no surprise a whole new ecosystem of tools has come along to help developers and architects acclimate to this new world. Docker and Kubernetes anyone? What tools and frameworks are you using? How have you or your team made the change? Is the architecture you work within a help or a hindrance?

2:15pm–3:05pm Tuesday, February 27, 2018
Mostly serverless
Location: Regent
Secondary topics:  Best Practice, Case Study
John Chapin (Symphonia)
Average rating: ***..
(3.33, 6 ratings)
Even EC2 has serverless attributes, and you can leverage them to realize the benefits of serverless in your classic enterprise cloud architectures. John Chapin shares the true story of an enterprise IT organization for which a potent combination of “mostly serverless” technology and a DevOps mindset have laid the groundwork for a future serverless transformation. Read more.
3:50pm–4:40pm Tuesday, February 27, 2018
Strategies for decentralized data management in microservices architectures
Location: Sutton North
Secondary topics:  Best Practice, Overview
JP Morgenthal (DXC)
Average rating: **...
(2.30, 20 ratings)
A big part of microservices architecture is decomposing monolithic applications with tightly coupled data models, but moving to decentralized data management is one of the most challenging aspects of a microservices architecture. JP Morgenthal shares strategies for your redesign efforts, the possible pitfalls, and the trade-offs these approaches force architects and engineers to make. Read more.
3:50pm–4:40pm Tuesday, February 27, 2018
Edge PaaS: A Netflix case study about edge service architecture
Location: Grand Ballroom West
Secondary topics:  Case Study
Tags: cloud, native
Paul Bakker (Netflix)
Average rating: ***..
(3.80, 5 ratings)
How do feature teams (device teams, UI, etc.) connect efficiently to backend services in a microservices architecture? How do you create an edge API that satisfies teams with vastly different requirements? And how do you operate these mission-critical edge services? Paul Bakker discusses these challenges and offers an overview of Netflix's PaaS built specifically for edge services. Read more.
4:50pm–5:40pm Tuesday, February 27, 2018
Y2K and other disappointing disasters: Risk reduction and harm mitigation
Location: Sutton North
Secondary topics:  Anti-Pattern, Best Practice
Heidi Waterhouse (LaunchDarkly)
Average rating: ****.
(4.40, 5 ratings)
Heidi Waterhouse explores risk reduction and harm mitigation, helping you understand where you can prevent problems and where you can just make them less bad, and shares available tools to make every disaster a disappointing fizzle. Read more.
1:15pm–2:05pm Wednesday, February 28, 2018
Observable microservices
Location: Regent
Secondary topics:  Best Practice, Overview
Maria Gomez (BCG Digital Ventures)
Average rating: ***..
(3.67, 9 ratings)
Think of this talk as Microservices 201. You know microservices basics and their pros and cons and have maybe even started putting them in production but haven't spent much time thinking about how to maintain them. Maria Gomez explores the most important operational concerns for maintaining microservices and explains why observability helps you maintain a healthy production environment. Read more.
2:15pm–3:05pm Wednesday, February 28, 2018
Logs are not human scale: How to build observable systems
Location: Mercury Ballroom
Secondary topics:  Anti-Pattern, Best Practice
Sam Stokes (Honeycomb)
Average rating: ****.
(4.00, 10 ratings)
In the complex world of microservices and distributed systems, we need to understand what our software is doing. Traditional tools, such as logs, read by humans and filtered by crude rules, aren’t powerful enough. Sam Stokes explains that we need new, better tools and why this will also require us to design our systems to give the tools better data. Read more.
3:50pm–4:40pm Wednesday, February 28, 2018
Why Netflix built an evolutionary architecture
Location: Mercury Ballroom
Secondary topics:  Best Practice, Case Study
Suudhan Rangarajan (Netflix)
Average rating: ****.
(4.83, 6 ratings)
As Netflix continues its journey beyond 100M members, the company is rearchitecting its critical Playback API service to better serve its business needs for the next three to five years. Suudhan Rangarajan discusses why and how Netflix rebuilt the Playback API service and outlines a rigorous framework that you can use to reason about your microservice architecture. Read more.
4:50pm–5:40pm Wednesday, February 28, 2018
REPEAT SESSION: Observable microservices
Location: Beekman Parlor
Secondary topics:  Best Practice
Maria Gomez (BCG Digital Ventures)
Average rating: ****.
(4.00, 2 ratings)
Think of this talk as Microservices 201. You know microservices basics and their pros and cons and have maybe even started putting them in production but haven't spent much time thinking about how to maintain them. Maria Gomez explores the most important operational concerns for maintaining microservices and explains why observability helps you maintain a healthy production environment. Read more.