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

Schedule: Cloud native sessions

Cloud native applications provide organizations with greater agility, resilience, and portability across cloud environments. As its core, this software design approach contains five key architectural principles: infrastructure-as-a-service, microservices, automation, containerization, and orchestration. Cloud native works well with continuous delivery, is highly scalable, and can be very efficient to operate, reducing risk along the way. With that said, confronting this new design landscape can feel quite daunting. Which public cloud provider should you choose? Are you even ready for public cloud, or do you need to focus on private cloud? And these questions are only the beginning. Soon you’ll need to consider IaaS versus PaaS, containers versus unikernels, Kubernetes versus Swarm, servers versus serverless—the list goes on. How can software architects and developers make sense of these choices to discover the best cloud native solutions for their organization?

9:00am - 5:00pm Sunday, February 25 & Monday, February 26
Applying cloud architecture patterns
Location: Concourse C
Matt Stine (Pivotal)
If you want to implement key design patterns and concepts in enterprise projects, there are clear architectural concepts and patterns that you can use as guideposts on your journey to the cloud. Matt Stine helps you understand six key architecture qualities: modularity, observability, deployability, testablity, disposability, and replaceability. Read more.
9:00am–12:30pm Monday, February 26, 2018
Continuous delivery in an ephemeral world
Location: Sutton North
Secondary topics:  Best Practice
Tags: cloud, native
John Chapin (Symphonia)
Average rating: ***..
(3.67, 6 ratings)
With systems like Travis CI, Circle CI, and CodeBuild, we're never more than a few lines of YAML away from a complete continuous delivery pipeline. However, ephemeral build systems constantly recreate the world from scratch, increasing build time and lengthening the CD feedback loop. John Chapin addresses those challenges and shares a reference pipeline using AWS CodePipeline and CodeBuild. Read more.
1:15pm–2:05pm Tuesday, February 27, 2018
Data services: Processing big data the microservice way
Location: Mercury Ballroom
Secondary topics:  Case Study, Overview
Mario-Leander Reimer (QAware)
Average rating: ***..
(3.17, 6 ratings)
Mario-Leander Reimer explores key JEE technologies that can be used to build JEE-powered data services and walks you through implementing the individual data processing tasks of a simplified showcase application. You'll then deploy and orchestrate the individual data services using OpenShift, illustrating the scalability of the overall processing pipeline. Read more.
1:15pm–2:05pm Tuesday, February 27, 2018
Building stream processing as a service at Netflix
Location: Grand Ballroom West
Secondary topics:  Best Practice, Case Study
Steven Wu (Netflix)
Average rating: **...
(2.42, 19 ratings)
Steven Wu explains how Netflix’s SPaaS platform empowers users to focus on extracting insights from data streams and build stream processing applications and shares lessons learned building and operating the largest SPaaS use case: Netflix’s Keystone data pipeline, a self-serve platform for creating near-real-time event pipelines that processes three trillion events and 12 PB of data every day. 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
Apache Kafka + Apache Mesos = Highly scalable streaming microservices
Location: Mercury Ballroom
Secondary topics:  Framework-focused, Hands-on
Kai Wähner (Confluent)
Average rating: ****.
(4.00, 2 ratings)
Kai Wähner shares a highly scalable, mission-critical infrastructure using Apache Kafka and Apache Mesos: Kafka brokers are used as the distributed messaging backbone; Kafka’s Streams API embeds stream processing into any external application without the need for a dedicated streaming cluster; and Mesos is used as a scalable infrastructure to leverage the benefits of a cloud-native platform. Read more.
4:50pm–5:40pm Tuesday, February 27, 2018
Continuous delivery patterns for contemporary architecture
Location: Regent
Secondary topics:  Best Practice, Case Study
Tags: cloud, native
Daniel Bryant (Datawire)
Average rating: ****.
(4.40, 10 ratings)
It's evident that modern software architecture is evolving toward fully component-based architectures, but there are many challenges to delivering such applications in a continuous, safe, and rapid fashion. Daniel Bryant shares a series of patterns to help you identify and implement solutions for continuous delivery of contemporary service-based architectures. Read more.
9:50am–10:10am Wednesday, February 28, 2018
Going (cloud) native
Location: Grand Ballroom
Tags: cloud, native
Kevin Stewart (Heptio)
Average rating: ***..
(3.14, 14 ratings)
Many organizations are racing to adopt cloud native to unlock all of the benefits that microservices, containers, and orchestration tools such as Kubernetes promise to deliver. Kevin Stewart explores the people, processes, and cultural aspects that complement the cloud-native computing technology stack. Read more.
3:50pm–4:40pm Wednesday, February 28, 2018
API security in a microservice architecture
Location: Grand Ballroom West
Secondary topics:  Best Practice, Overview
Matthew McLarty (MuleSoft)
Average rating: ****.
(4.17, 12 ratings)
Microservices have taken the software architecture world by storm. Initially driven by a desire for increased delivery velocity and greater scalability, organizations are now recognizing the importance and complexity of securing their microservices. Matt McLarty shares techniques for securing microservice APIs and a practical model you can implement in your organization. Read more.
4:50pm–5:40pm Wednesday, February 28, 2018
Evolving a modern end-to-end data infrastructure at Comcast
Location: Mercury Ballroom
Secondary topics:  Best Practice, Case Study
Michael Bevilacqua-linn (Facebook)
Average rating: ***..
(3.83, 6 ratings)
Michael Bevilacqua-linn shares an architecture for a cloud-based end-to-end data infrastructure that handles everything from classic analytic use cases to real-time operational analysis to modern machine learning techniques in an elastically scaleable and secure manner. Read more.
4:50pm–5:40pm Wednesday, February 28, 2018
The second-hardest part of microservices: Calling your services
Location: Regent
Secondary topics:  Best Practice, Framework-focused
Christian Posta (solo.io)
Average rating: ****.
(4.67, 3 ratings)
When building microservices, you must solve for a number of critical functions, but the process can be incredibly complex and expensive to maintain. Christian Posta offers an overview of Envoy Proxy and Istio.io Service Mesh, explaining how they solve application networking problems more elegantly by pushing these concerns down to the infrastructure layer and demonstrating how it all works. Read more.
4:50pm–5:40pm Wednesday, February 28, 2018
How Shutterstock built a component-based 12-factor application
Location: Grand Ballroom West
Secondary topics:  Best Practice, Framework-focused
Marty Brodbeck (Shutterstock)
Average rating: ****.
(4.00, 2 ratings)
In an effort to consolidate and modernize the company’s technology stack, Shutterstock recently embarked on a technology overhaul, which also led to organizational and cultural change. Marty Brodbeck shares some of the decisions Shutterstock made and the challenges it faced during this huge transformation, along with key principles that drove and guided the shift. Read more.