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

Understanding the terms of testing

First, let’s get some of the definitions out of the way before we continue. Let’s start with the types of tests:

  • Unit tests: Unit tests involve testing every function individually and making sure that, given a certain expected and unexpected input, the function responds with an expected output or a graceful error.
  • Integration tests: Integration tests are a higher level of testing than unit tests and often involve various modules for each scenario. Some integration testing scenarios might involve various functions and modules that make sure these functions work well in tandem to deliver certain functionality.
  • End-to-end (E2E) tests: These tests provide the highest level of testing, which often involves running test scenarios against a live system.
  • Regression testing: These types of tests are run to find inconsistencies and broken behavior when the system changes.

I won’t go about arguing the case for...