Good points. I had a few things I disagreed on but the one I want to highlight is the rollback ability which use case is this not possible? When I deploy infra as code it’s my responsibility to ensure that the design can be rolled back. In some cases where data is involved it may require some backups like you said but the same thing applies with app code
Hey thanks for your comment, the ability to roll back is definitely responsibility of the team managing the IaC, but doing that in the same way is done with application is not always easy to achieve (or can have considerable cost implications, I am thinking at Blue/Green provisioning strategy for instance). Any type of accidental change, deleting a resource for example, may take longer compared to the application scenario where you go back to the previous version.
Good points. I had a few things I disagreed on but the one I want to highlight is the rollback ability which use case is this not possible? When I deploy infra as code it’s my responsibility to ensure that the design can be rolled back. In some cases where data is involved it may require some backups like you said but the same thing applies with app code
Hey thanks for your comment, the ability to roll back is definitely responsibility of the team managing the IaC, but doing that in the same way is done with application is not always easy to achieve (or can have considerable cost implications, I am thinking at Blue/Green provisioning strategy for instance). Any type of accidental change, deleting a resource for example, may take longer compared to the application scenario where you go back to the previous version.
Great video, Anto.
Great video man!
Glad you liked it!
❤
Infrastructure as code is code in DECLARATIVE rather than IMPERATIVE paradigm.