Implementing a cloud strategy

Sound advice would recommend starting the migration with workloads that are not business-critical or that can be easily moved. For the most complex work or work that is business-sensitive, hand-to-hand support may be appropriate. In other respects, it would be necessary to consider the rewriting of certain applications, in DevOps or otherwise, even if it is only to redistribute the workloads over several servers.

It is obvious that this goes beyond a simple technological evolution.It is a new state of mind, a new way of thinking about business and organisation and so  it  becomes a new way of steering, of monitoring

Yet too many executives view Cloud migration as a convenience, a necessary transition from a proprietary information system to a cloud infrastructure. This is a fundamental error because, while budget issues are no longer an obstacle, they require a comprehensive view of commitments right from the strategy definition stage. Let's be clear on this point: at an iso scope, the cloud offers no savings over an "on prem" environment, even if the level of service is improved.

The benefits of the cloud must be considered in terms of meeting business needs, rather than infrastructure. It must be considered in terms of possible pooling and economies of scale, rather than ROI. It must be considered in terms of retaining talent rather than their payroll.

Identifying and implementing the right solution or the right type of cloud based on specific business characteristics and objectives is becoming a key issue.

While hybrid and multi-cloud platforms are becoming the norm, due to a reasoned choice where the desire to not depend on a single provider is paramount, the choice of a cloud at the scale of an application or a specific service depends on numerous factors that each company will have to determine.