Popular Continuous Integration tools like Jenkins, TeamCity, TravisCI, CircleCI, and Gitlab allow you to trigger provisioning and configuration of required infrastructure based on a code artifact. By using IaC and configuration management tools, you enable your cloud infrastructure provisioning and configuration to be triggered by a code change. Again, these tools allow you to write and maintain code that describes the configuration of your infrastructure.Īnother opportunity for automation is in your delivery pipeline. There should be no excuses when it comes to exploiting this convenience, but too many do not.Īdditionally, tools such as Puppet, Chef, and Ansible have gained IaC capabilities, but are most notably configuration management tools designed to install and manage software on existing servers/VMs. You have the opportunity to code immutable infrastructure declaratively (including databases, load balancers, and network), and manage it using existing version control systems. This shift enables programmable infrastructure (Infrastructure-as-Code) through tools like Terraform, Heat, AWS CloudFormation, and Azure Resource Manager. One of the wonderful perks of the cloud is that resources can be provisioned and managed using clean, well-documented APIs. Essentially, every step that requires manual intervention is costly and risky. While it’s not a cloud-specific deficit, it is typically a much lower investment to automate in the cloud, as opposed to on-premises. Why start off on the wrong foot? What is cloud debt? Immediate Debt: Lack of Automationįailure to automate infrastructure, configuration, or delivery pipeline creates cloud debt in the form of maintenance costs, time, and risk. In fact, moving to the cloud is often part of large modernization efforts intended to eliminate decades of existing technical debt. We should be capitalizing on the opportunities available to maximize gains, especially when they require little up-front investment. The primary business drivers for leveraging the cloud are reducing cost, decreasing time-to-market, and gaining business agility. Many newer companies that have leveraged the cloud since their inception have unknowingly, or often knowingly, accrued cloud debt. As organizations move infrastructure to the cloud, they have the opportunity to eliminate existing debt, but also risk creating it. It comes in many forms and is difficult to identify in many cases, but one thing is for certain - it has compounding costs. If you have spent any time working at a company that relies on technology, you have most likely felt the impacts of technical debt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |