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, new ways of thinking about activities and the organization. This means new ways of managing and monitoring

Too many managers consider migration to the cloud as a commodity, an obligatory transition between a proprietary IS and a cloud infrastructure. This is a fundamental mistake, because even if the budget issue is no longer an obstacle, it requires a global view of commitments from the strategy definition stage. Let's be clear on this point: on an isolated basis, 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. On the possible mutualization and economy of scale, more than on the ROI. On the retention of talent more than their payroll ...

Identifying and implementing the right solution or type of cloud according to specific business objectives is becoming a key issue.

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