AWS CDK Day 2023 - CDK Best Practices

[@chikosan99]

Great! Thanks

[@illyam689]

Thanks! Very clear and straight to the point!

[@ranthebuilder]

Thanks!

[@SamuelCarreira]

Thanks for the video. When you are talking about a single stack you are not referencing the nested stacks approach right? I’m asking because a “simple stack” can reach the resources limit

[@ranthebuilder]

Nested stacks are a great solution to overcome resource limit in CF

[@artemvolkov8364]

Thank you for the experience. About one stack is questionable. I am using Stages to group stacks. Separate stacks with storage and application by criticality (in case if stack with Lambda fails I don't want to allow DB stack to fail) and by frequency of deployment (I am not changing for example RDS a lot so I don't want to touch this stack.)

[@ranthebuilder]

Yeah, there are no hardcore rules. Rds is a good option to move to a different stack but it can work in a single stack too. We moved it to a different stack so all developers working on the same account would not deploy aurora but share one db and create their own table

[@artemvolkov8364]

@@ranthebuilder We are doing the same for such "shared" resources. They are in a separate CDK application "Core Infrastructure" with an outputs to SSM Parameter store

[@richardferneygarcia]

So, am I wrong when into the same project I create two Stacks?

[@ranthebuilder]

Not wrong, but it's riskier. I don't recommend it.