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

A Starter Project and Core Concepts

At Westpoint, we’ve been invested in the Cloud Development Kit (CDK) platform right from the early days when we discovered the potential productivity gains. You will discover more about these potential gains later in the following chapters as we introduce new approaches to cloud solution architecture that this awesome new tool brings.

As a result of our constant curiosity toward CDK and later using it to deliver projects, we have come up with some good practices for organizing CDK-based applications. These practices revolve essentially around code organization and should not be considered complete, by any means, since we are still on this journey ourselves and we add things as we discover them. It works for us, so it might work for you. We would also love to hear of other ways CDK projects can be integrated into other modern workflows. So, if you have such suggestions, please reach out to us via any of our public GitHub repos.

In this...