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

Introduction to CI/CD

Before jumping into action, we wanted to take some time to introduce you to some concepts about CI/CD and explain why even though it’s imperfect, AWS’s CI/CD toolset fits CDK projects the best.

What is continuous integration (CI)?

Put simply, CI is the process of creating different branches for bug fixes and features in your projects. Once the results are satisfactory, you can go ahead and merge these changes into the main branch. By satisfactory results, we mean the code is reviewed and well tested.

While CI is in the most part a development procedure issue, there are elements of CI that need to be automated. We don’t know about you, but we wouldn’t be able to trust the word of every developer who has run the tests that everything was green and OK. This integration needs to happen automatically and the results must be reported.

What is continuous delivery (CD)?

Once the steps from the CI process are complete, CD kicks...