What about operational transformation?

[rakhirhif8963]

However, there is a danger in delving too deeply and getting stuck on individual processes. Each process is part of a larger whole, and interfering with one or two processes in isolation can have unexpected consequences for the entire organization.

John Collins, vice president of Gigaom and former CTO, believes that platform engineering is certainly an evolution of DevOps, which was aimed at accelerating the delivery of software and services and, more importantly, ensuring their continuity, without having to think about the underlying infrastructure. Platform engineering recognizes that argentina mobile database need to understand the underlying infrastructure and design it in advance.

But, Collins continues, “the problem with digital transformation is that it directly affects operating models. It’s not enough to say, ‘Hey, we just need to change.’”

In his view, a cloud-native approach may be sufficient for individual applications, and even for a few applications built in a similar way. “But it’s not sufficient for a massive, complex infrastructure where you have things that have been around since the 1960s, things that have been around since the 1990s, things that have been around since last week that weren’t built correctly,” he says.

Collins says the policy-as-code model is useful, but it’s not enough on its own to address the challenges facing operations staff: resource and time constraints, skills shortages, and all the rest. He believes that to make real progress, operations teams need advances in visibility, insights, and automation.

"If your operational processes are inefficient or imperfect, you may end up with inefficient automation. You're just making the problem worse or putting a band-aid on it," Collins says.