Advanced ways that CDK is leveraged
In the last chapter, we covered ISAA, our preferred ways of creating cloud applications that stand the test of time so well that we seldom need to conduct any infrastructure maintenance procedures. As CDK adoption is increasing, we are seeing interesting infrastructure patterns emerge. In this section, we will cover some of these new and interesting ways companies are using CDK to respond to infrastructure challenges that previously required heavy development work that made them out of reach for start-ups and other small tech businesses.
Creating multiple CDK stacks
For the sake of simplicity, we have so far been mainly working with a single CDK stack in each CDK app. As mentioned before, AWS CloudFormation has limit of 500 resources per stack. You might think this is a large number, but when you deal with serverless applications and deploy many Lambda functions and their dependencies such as roles and layers, you will hit this limit.