Book Image

AWS CDK in Practice

By : Mark Avdi, Leo Lam
Book Image

AWS CDK in Practice

By: Mark Avdi, Leo Lam

Overview of this book

As cloud applications are becoming more complex, multiple tools and services have emerged to cater to the challenges of running reliable solutions. Although infrastructure as code, containers, and orchestration tools, such as Kubernetes, have proved to be efficient in solving these challenges, AWS CDK represents a paradigm shift in building easily developed, extended, and maintained applications. With AWS CDK in Practice, you’ll start by setting up basic day-to-day infrastructure while understanding the new prospects that CDK offers. You’ll learn how to set up pipelines for building CDK applications on the cloud that are long-lasting, agile, and maintainable. You’ll also gain practical knowledge of container-based and serverless application development. Furthermore, you’ll discover how to leverage AWS CDK to build cloud solutions using code instead of configuration files. Finally, you’ll explore current community best practices for solving production issues when dealing with CDK applications. By the end of this book, you’ll have practical knowledge of CDK, and you’ll be able to leverage the power of AWS with code that is simple to write and maintain using AWS CDK.
Table of Contents (17 chapters)
Part 1: An Introduction to AWS CDK
Part 2: Practical Cloud Development with AWS CDK
Part 3: Serverless Development with AWS CDK
Part 4: Advanced Architectural Concepts

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...