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

Continuous delivery patterns for contemporary architecture

Daniel Bryant (Datawire)
4:50pm–5:40pm Tuesday, February 27, 2018
Cloud native, Microservices
Location: Regent
Secondary topics:  Best Practice, Case Study
Tags: cloud, native
Average rating: ****.
(4.40, 10 ratings)

Who is this presentation for?

  • Architects and senior developers

Prerequisite knowledge

  • Experience with microservices

What you'll learn

  • Understand how contemporary architectures like SCS, microservices, and serverless impact continuous delivery, how to ensure that this is factored into the overall software design, and how to create a build pipeline to deliver these architectures in a safe and rapid fashion
  • Learn how continuous delivery, service contracts, and end-to-end validation support the delivery of correct software
  • Discover the benefits and drawbacks of implementing consumer-driven contracts (CDC) and message contract validation


Last year at this conference we learned from Mark Richards that modern software has almost completed its evolution toward component-based architectures—seen in the mainstream embrace of self-contained systems (SCS), microservices, and serverless architecture. We all know the benefits of component-based architectures, but there are also 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.

Topics include:

  • The core stages in the component delivery lifecycle: Develop, test, deploy, operate, and observe
  • How contemporary architectures impact continuous delivery and how to ensure that this is factored into the design
  • Modifying the build pipeline to support testability and deployability of components (with a hat tip to Jez Humble’s and Dave Farley’s seminal work)
  • Commonality between delivery of SCS, microservices, and serverless components
  • Continuous delivery, service contracts, and end-to-end validation: The good, the bad, and the ugly
  • Validating NFRs within a service pipeline
  • Lessons learned in the trenches
Photo of Daniel Bryant

Daniel Bryant


Daniel Bryant is an independent technical consultant and product architect at Datawire, where he specializes in enabling continuous delivery within organizations through the identification of value streams, the creation of build pipelines, and the implementation of effective testing strategies. Daniel’s technical expertise focuses on DevOps tooling, cloud and container platforms, and microservice implementations. He contributes to several open source projects, writes for InfoQ, O’Reilly, and Voxxed, and regularly presents at international conferences, including OSCON, QCon, and JavaOne.