{"id":20753,"date":"2022-03-02T11:22:54","date_gmt":"2022-03-02T10:22:54","guid":{"rendered":"https:\/\/beta.cybus.io\/resources\/glossar\/ansible-2-2-2-2-2-2-2-2-2-2-2\/"},"modified":"2023-09-22T14:16:46","modified_gmt":"2023-09-22T12:16:46","slug":"infrastructure-as-code","status":"publish","type":"page","link":"https:\/\/www.cybus.io\/en\/resources\/glossary\/infrastructure-as-code\/","title":{"rendered":"Infrastructure as Code"},"content":{"rendered":"\n
\n
\n
back to glossary<\/a><\/div>\n<\/div>\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n

What is Infrastructure as Code?<\/h1>\n\n\n\n

Infrastructure as Code describes the process of deploying and managing IT infrastructure through auditable configurations (e.g., YAML<\/a> files) from a centralized repository.<\/strong> <\/p>\n\n\n\n

Instead of installing devices manually, an Infrastructure as Code (IaC) environment collects and provides all details for setup and running a device over a network. This approach reduces management and maintenance efforts while minimizing human error at setup. Also, in cloud-based solutions and in clustering devices, IaC is a key element to improve scalability and a fast and reliable deployment of homogeneous systems.<\/p>\n\n\n\n

What are the advantages of Infrastructure as Code?<\/h2>\n\n\n\n

Compared to No-Code and Low-Code solutions, the IaC approach unfolds its advantages especially for larger and more complex setups: Once a configuration file has been written, it can be applied to identical machines or assets in seconds. Implementing additional assets in this way is more than 95% faster than with a regular setup. Configuration files also enable automated rollouts. Here, too, the user not only benefits from speed, but can also rule out errors that would have been possible with manual implementation.<\/p>\n\n\n\n

The IaC approach is cloud-native. It can be easily deployed with technologies such as Ansible<\/a>, Kafka and Kubernetes<\/a>.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n
\n
\n

Easily explained with Cybus Learn<\/h3>\n\n\n\n

The IaC-approach describes an entire infrastructure, needed for an IIoT use-case, in only one structured text file \u2013 often called the configuration or commissioning file. This file lists all of its components, called resources, and defines their specifications and interrelations in a standardized way. The commissioning file thus avoids time-consuming maneuvering of separate configurations or even scripts for each and all the different elements needed in a use-case. Everything is in one place, structured and standardized.<\/p>\n\n\n\n

\n
full article<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\"\"<\/a>
A comparison with no-code\/low-code platforms (top) and IaC platforms (bottom) shows how configurations are realized faster and less error-prone in the IaC approach.<\/figcaption><\/figure>\n<\/div>\n<\/div>\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n
\n
back to glossary<\/a><\/div>\n<\/div>\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n

You might also be interested in<\/h2>\n\n\n\n

Industry news, recent news and valuable use cases<\/h3>\n\n\n
\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t