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?
- Introduction to Deployment Pipelines
- Deployment Pipeline Stages
- Building Integration Pipelines
- Fan In Fan Out
- Deployment Pipeline Challenges
- Verifying Forward Backward Compatibility
- Testing Practices
- Continuous Integration and Trunk-Based Development
- Incremental Deployment Strategies
- Data Management Migration
- Continuous Delivery for Architects
- Microservices Introduction
- Microservices Design
- Microservices Integration
- Microservices Refactoring
- Engineering Practices for Microservices Part 1
- Engineering Practices for Microservices Part 2
- Engineering Practices for Microservices Part 3
- Title: Engineering Practices for Continuous Delivery
- Release date: March 2015
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781491908181
You might also like
Head First Design Patterns, 2nd Edition
You know you don’t want to reinvent the wheel, so you look to design patterns—the lessons …
Software Architecture Fundamentals, Second Edition
Being a successful software architect is more than just possessing technical knowledge. It’s about thinking like …
O'Reilly Software Architecture Conference 2019 - New York, New York
What do you really need to consider when adopting a microservices architecture? How do you unite …
Software Engineering at Google
Today, software engineers need to know not only how to program effectively but also how to …