Book Image

AWS CDK in Practice

By : Mark Avdi, Leo Lam
3.5 (2)
Book Image

AWS CDK in Practice

3.5 (2)
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)
1
Part 1: An Introduction to AWS CDK
4
Part 2: Practical Cloud Development with AWS CDK
9
Part 3: Serverless Development with AWS CDK
12
Part 4: Advanced Architectural Concepts

Limitations of LocalStack

We dislike it when a solution to a certain problem is proposed without covering the limitations of that solution. All of that is left for the developers to find out themselves (looking at you, AWS docs) through trial and error, potentially wasting hours or days on a solution that might not be the right one for them.

We’ve presented LocalStack as a silver bullet for local serverless development, but it too comes with limitations that you might find annoying or impossible to work with. In our company, we use LocalStack on some projects and not on others, mainly depending on the AWS services we are using.

One of the main limitations is that LocalStack may not fully replicate the behavior of some AWS services. For example, the behavior of the S3 service in LocalStack may differ from that of AWS’s actual S3 service, which can lead to unexpected errors or behavior when the code is deployed to production. Additionally, not all AWS services are...