In a follow-on to his well-received tutorial from last year’s SACON, Symphonia’s John Chapin offers an overview of existing cloud-native build systems and outlines their benefits and drawbacks, including cost efficiency, environment stability, and provenance. Drawing on a real-world use case involving a Maven-based build and a serverless application architecture, John walks you step-by-step through the various stages of a naive continuous delivery pipeline, including source control integration, artifact builds, and an infrastructure-as-code-style deployment. John concludes by demonstrating an optimized continuous delivery pipeline that incorporates advanced CodePipeline and CodeBuild techniques to reduce the overall build time and shrink the continuous delivery feedback loop while still realizing all of the benefits of an on-demand, ephemeral build system.
Note: While John will cover the same basics as his tutorial last year, all examples will be updated to reflect the latest CodePipeline and CodeBuild features.
Sample code and infrastructure templates will be made available.
John Chapin is a cofounder of Symphonia, an expert consultancy based in New York City that helps companies of all sizes use serverless and cloud technology to deliver value quickly and effectively. Along with Symphonia cofounder Mike Roberts, John authored the recent O’Reilly report, What Is Serverless? His and Mike’s highly regarded talks and workshops are regularly featured at conferences such as Software Architecture Conference, Velocity, OSCON, QCon, ServerlessConf, and AWS re:Invent. John can be reached at email@example.com.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org