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

Advantages of ISAA

We don’t necessarily split atoms in our organization, but we develop extremely reliable business applications. Businesses are seeing the huge advantages of serverless; combine that with event-driven architecture and a few other tweaks, and the result is that we are right now running numerous serverless applications. We find that sometimes we leave code that perfectly suits a problem running for so long without issues that we forget how it worked in the first place – essentially, realizing that we have to document our software much better going forward. But hey, we’ll take that over sleepless nights trying to resolve scaling issues any day.

Our resources, the most important of which is our time, are not then spent on keeping software running but on shipping new features and working on new projects and ideas. Our engineers are a lot happier, more engaged, and creative and our customers love the reliability of the systems we produce.