More Related Content Similar to "AWS CDK. Infrastructure as a code with TypeScript", Yurii Myrosh (20) "AWS CDK. Infrastructure as a code with TypeScript", Yurii Myrosh2. 2
LEMBERGSOLUTIONS.COM
© 2022, Lemberg Solutions LLC. All rights reserved
Experience
About me
11 years
Position
Head of Javascript Department at Lemberg Solutions
Technologies
Node.js, NestJS, Angular, React, AWS
Legacy
PHP, Contao CMS, CodeIgniter, Kohana, FuelPHP, Laravel
35. 35
LEMBERGSOLUTIONS.COM
© 2022, Lemberg Solutions LLC. All rights reserved
Summary
Pros Cons
● Development budget (every your developer
should have AWS account)
● There is no local emulator so it is hard to
perform local testing. There is possibility to
use SAM but it is not the same as deploying
stacks.
● Hard to implement e2e tests.
● Infrastructure as a code.
● Ability to keep services in the same repo with your
application.
● Easy configuration of environments.
● Permissions management
● Unit testing can be really easy
● It is possible to develop applications without devOps
(not really true, because your developers need to know
devOps part)
36. 36
LEMBERGSOLUTIONS.COM
© 2022, Lemberg Solutions LLC. All rights reserved
Links
● https://docs.aws.amazon.com/cdk/v2/guide/home.html
● https://docs.aws.amazon.com/cdk/api/v2/index.html
● https://constructs.dev/
● https://github.com/yuriymyrosh/cdk_demo
● https://www.linkedin.com/in/yuriy-myrosh/
● https://www.facebook.com/yura.myrosh/