Infrastructure as data - why should you care? By Gerald Schmidt
Defining cloud infrastructure as code has gone from best practice to how we all work in the space of a few years. For developers, this means increased portability and fewer moving parts. For Amazon's rivals, the barrier to entry is no longer 150 individual service offerings, but a robust managed Kubernetes service.
We cannot afford to ignore this trend. For our clients, the choices are more nuanced. We need to help them weigh the benefits of infrastructure as data against the risk of committing too soon, before the approach is ready in terms of ease of use, availability and durability.
https://www.thoughtworks.com/infrastr...