Infrastructure, cost, and the cloud

You need to think about infrastructure as a set of components. How do you assemble those components and then interact with them? In addition to that, how do you keep everything evolving? Infrastructure is much more elastic—to use a cloud term—than static, as it was before. Applications that live on top of that used to have the monolithic stacks or classic three-tiered architecture, but nowadays with containers, VMs, and microservices-based architectures, that's changed rapidly. It's why everybody needs to understand from an engineering perspective how the application or a set of services behave. It's also why they keep tracking that and looking for anomalies, because that's how you make sure that the site or your service is more reliable.

Viktor Farcic: What prevents companies from going to the cloud? Many of those that I've communicated with still tend to reject it, or maybe I'm just unlucky with the...