When creating a continuous delivery pipeline, many strive only to automate what they’re already building instead of taking another look at old assumptions. When your goal is to deploy once a quarter, you may choose an architecture with tightly coupled services or components. If your goal is to be able to deploy on demand, this same architecture may be getting in your way.
Join Ken Mugrage (ThoughtWorks) to discover how changing the architecture of your system to enable faster delivery can be more beneficial and stable than trying to automate deployment for systems that weren’t designed for it. Closely related to the ability to deploy the application on demand is the ability to make sure it’s doing what we expect it to every time. Acceptance tests, especially when browser based, are often considered so fragile that many organizations have simply stopped doing them. Ken shows you how to make architectural decisions that will make it easier to write and maintain quality-acceptance tests.
- Title: Architecting for testing and continuous delivery
- Release date: December 2019
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 0636920362111
You might also like
O'Reilly Velocity Conference 2019 - Berlin, Germany
O'Reilly Velocity Conferences are devoted to providing its international audience of SREs, app developers, DevOps practitioners, …
Infrastructure as Code, 2nd Edition
Just five years ago, infrastructure as code was a new concept for many companies. Today, even …
Go is rapidly becoming the preferred language for building web services. There are plenty of tutorials …
51+ hours of video instruction. Overview The professional programmer’s Deitel® video guide to Python development with …