AWS CDK is a first step towards treating IaC as a first-class code citizen in our projects. It can enable many new use cases. However, in a multi-cloud environment, we are still facing the domination of Terraform. But, what if other cloud providers would adopt this approach?
This question popped into my mind recently. After several sessions with the AWS CDK, when I worked through typical tasks that we all do as a Cloud Architect/DevOps Engineers on AWS, I realized that in the Infrastructure as Code space, we did not arrive at any breakthrough recently.
A longer article about my research, how AWS used formal methods – in particular TLA+ to design their outstanding services like DynamoDB, EC2 or S3.
If you are struggling with the choice of the cloud computing vendor and you are choosing between AWS and GCP, you may be interested in the following article.
I tried to show you the benefits of Amazon Web Services and when is it smarter to choose AWS over the Google’s Cloud.
Choosing the best tool for your Infrastructure as Code is not an easy task. From one hand you are aware of the risks coming from the cloud providers including vendor lock-in. From the other hand, external tools impose many limitations. How to wisely choose the proper one? Let’s find out!