Releasing software to actual users can be a painful, risky, and time-consuming process. With this video workshop, experienced developers, testers, and operations engineers learn the principles and technical practices that enable rapid, incremental delivery of new, high-quality, valuable functionality to users.
This video from Neal Ford (and guest experts Tim Brown, Rachel Laycock, and Ryan Murray) demonstrates the engineering practices that allow you to get fast feedback on the production readiness of your application every time there is a change to the code, infrastructure, or configuration.
You’ll learn that, through automation of the build, deployment, and testing processes—and improved collaboration among developers, testers and operations engineers—delivery teams can get changes released in a matter of hours (sometimes even minutes), no matter how large or complex the project is.
- Introduction to deployment pipelines
- Deployment pipeline best practices with Cruise Go
- Testing practices
- Continuous integration
- Trunk-based development
- Incremental deployment strategies
- Data management and migration
- DevOps impact on all facets of a project
- Continuous delivery for architects
- Contract tests
- Engineering practices for microservices
- Metrics and monitoring
- Details on setting up deployment pipelines
- How continuous delivery works with Fan-in and Fan-out integration
- How to ensure automated backwards compatibility among evolving services
Neal Ford is Director, Software Architect, and Meme Wrangler at ThoughtWorks, a global IT consultancy. Proficient in a variety of languages, paradigms, and architectural styles, his primary consulting focus is the design and construction of large-scale enterprise applications.
About the O’Reilly Software Architecture Series
Clearing a path from developer to architect and enriching that path once you arrive
Software architecture is a massive multidisciplinary subject, covering many roles and responsibilities, and it is a fast-moving discipline where entire suites of "best practices" become obsolete practically overnight—yesterday’s best practice is tomorrow’s anti-pattern. No single path or curriculum exists; different types of architecture—application, integration, enterprise—require different subject emphasis. And yet, year after year, the job "software architect" places in the top ten of most Best Jobs surveys.
Keeping up with new approaches is challenging because you must maintain both technical depth and breadth. Whether you are at the outset of a career as an architect or in the midst of such a career, the O’Reilly Software Architecture series brings together a rich variety of topics, deep dives, innovative thinking, practical tips, and unfettered access to expert know-how that you can incorporate into a path that makes sense for you.
Table of contents
- What Problem Are We Trying to Solve? 00:26:12
- Introduction to Deployment Pipelines 00:22:50
- Deployment Pipeline Stages 00:16:12
- Building Integration Pipelines 00:23:14
- Fan In & Fan Out 00:22:34
- Deployment Pipeline Challenges 00:17:56
- Verifying Forward & Backward Compatibility 00:15:44
- Testing Practices 00:35:52
- Continuous Integration and Trunk-Based Development 00:25:50
- Incremental Deployment Strategies 00:14:39
- Data Management & Migration 00:24:19
- DevOps 00:29:35
- Continuous Delivery for Architects 00:38:53
- Microservices Introduction 00:24:18
- Microservices Design 00:20:40
- Microservices Integration 00:20:32
- Microservices Refactoring 00:13:55
- Engineering Practices for Microservices Part 1 00:27:18
- Engineering Practices for Microservices Part 2 00:26:45
- Engineering Practices for Microservices Part 3 00:41:44
- Title: Engineering Practices for Continuous Delivery
- Release date: March 2015
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491908181
You might also like
51+ hours of video instruction. Overview The professional programmer’s Deitel® video guide to Python development with …
The Principles of Microservices
What are microservices? When should you use them? Should you start with microservices, or migrate to …
Infrastructure as Code, 2nd Edition
Just five years ago, infrastructure as code was a new concept for many companies. Today, even …
Microservices designs require you to change how you build and deploy applications. Instead of creating a …