Continuous Delivery with CDK-Powered Apps

You’ve surely heard of continuous integration/continuous delivery (CI/CD) and most likely practiced it yourself in your projects. Take the example from the last chapter. We developed and deployed a full stack web application using AWS CDK. But that’s not where our work as developers stops. Software systems continuously evolve and need to incorporate changes to the code base. New features are added and bugs are fixed. New versions of software need to be rolled out.

The friction between developing code and deploying must be minimal, the reason being that having fewer deployments means that each deployment will have a lot of changes incorporated in it. With a lot of changes going on at once, you will have many ways in which things can go wrong. This ultimately causes a vicious circle, where more production releases go wrong and developers, as a result, become weary of releasing changes, which in turn exacerbates the problem of...