Introduction

Last year, I had the pleasure of participating in an expert discussion hosted by the German media outlet Computerwoche. This expert discussion was held as a moderated panel discussion between various panelists. Experts from a wide range of companies were invited to the discussion. An interesting and lively discussion emerged throughout the event, which lasted just under two hours. The panel discussion was documented by journalists. Following the discussion, two articles were written and published on the Computerwoche website.
The following quote from myself is reproduced in both articles:

The mantra ‘cloud first’ is changing to ‘application first’. Current multi-cloud usage has grown by accident over time at many companies, and this often creates a degree of complexity. At the same time, many new opportunities are emerging. We need to get to a point in the discussion where multi-cloud management is applied strategically, and aligned with business objectives. Using Google Cloud as an example alone, I can spontaneously think of five ways to host containers. A good strategy takes these options into account.
The first step is to conduct an application assessment to determine which application fits which landing zone. Once this has been done, a decision can be made as to whether it makes sense to operate an application in a cloud environment using lift-and-shift, or whether refactoring is perhaps the better approach.

First article - Multi-Cloud becomes Poly-Cloud

In the first article, the author Florian Stocker writes that among others the trend to consume software-as-a-service offerings has led to the creation of a heterogeneous multi-cloud environment within companies. The author describes IT governance as a major challenge for today’s IT operations since companies operate their own multi-cloud environment without consciously forcing it. IT teams nowadays have to manage this growing zoo of applications, which is difficult without an adapted strategy. The main focus should be on protecting critical business data and maintaining independence by avoiding vendor lock-in. Companies should be well advised to set themselves up to maintain or regain their sovereignty and invest in the right strategy accordingly.

Here the link to the article:
Article 1

Download the text directly:

Second article - How cloud native fuels your business

In the second article, author Lee Atchison writes how adopting Cloud-Native principles is about achieving the flexibility needed to remain competitive in an ever-changing market. The author describes how companies from various industries are adopting cloud-based infrastructures to support their digital transformation. However, just using a cloud operations model is not enough to achieve optimal flexibility, availability, scalability, and overall performance. Companies need to adopt Cloud-Native principles for application development and deployment. Cloud-Native applications are software systems developed according to the principles of the cloud as an operations model(dynamic, scalable, and highly available). Cloud-Native architecture is a response to the challenges faced by software developers when working with legacy approaches. Cloud-Native applications use dynamic resource allocation, service or microservice architectures, are containerized, orchestrated with e.g. Kubernetes, and store and manage data in cloud-managed databases and other data services.

Here the link to the article:
Article 2

Download the text directly:

Summary

First of all, the panel discussion was fun, very interesting to get to know and exchange different perspectives and opinions within an industry. Furthermore, it was very interesting to follow the process and to accompany how the articles for Computerwoche emerged from the panel discussion. Such sideline activities are welcome diversions from my daily work routine.