| Immutable infrastructure is an approach to virtual resource management in which a component is built, tested and deployed once and discarded if it needs to be changed. The word immutable means "unable to change." The concept of an immutable infrastructure is similar to the idea of using golden images. When a change is necessary, a new iteration is assembled, tested, validated and made available for use. The old iteration is then archived or deleted. An immutable infrastructure restricts the potential for configuration drift, which in turn can help reduce vulnerability to attack. Uptime can be improved during unexpected events, because instances are redeployed instead of having to be restored from multiple unique configurations and versions. If the new instance does not meet expectations, it can simply be rolled back to the last known good instance. Other benefits to an immutable infrastructure include lowering IT complexity and failures, improving security and reducing the need to troubleshoot problems in a production environment. For example, this approach eliminates server patching and configuration changes, because each update to the service or application workload initiates a new, tested and up-to-date instance. There is no need to track changes. If the new instance does not meet expectations, it is simply rolled back to the prior known-good instance. The concept of immutable infrastructure is in its formative stages and is often associated with cloud computing, virtualization and containerization. Currently, there is no single or uniform methodology or toolset for adoption. Related technologies such as IT orchestration, automation and resource management are still developing. | 
Posts
No comments:
Post a Comment