We see is that a lot of customers and companies are moving towards the cloud, but in many occasions they have no understanding what the hell. I was talking to one of our Enterprise Architects the other day and they basically had a request from the CIO to determine how many accountants and how many virtual machines the currently have in the cloud and interesting enough to had no clue. And they basically had to Send a developer out your two weeks to basically write some scanning routines and provide that simple answer to the CIO, only two weeks later.
Call native basically is a fitting new terminology this describes a number of Concepts that people are using when they move into the cloud and basically it describes a paradigm shift on on how you actually architecture and develop software. So it includes utilization of native cloud services. So package functionality, that you can basically directly take from the cloud provider and combines that with HR. As well as modern microservice architectures that basically decomposition, the architecture into a number of services that can run independent in order to deliver on the promise in the cloud which is full tolerance and adaptive scaling.
All companies, these days are basically part of a digital transformation, where the business model is undergoing. Fairly radical changes to, basically better employ digital Technologies and cognitive is one of the key drivers, that allows you to basically re-architecture on how you deliver your services. That’s why I called native is of such high importance to at least many of the customers that we talked to.
We see that most of our customers and most companies employ a multi-pronged strategy amongst probably between 80 and 90 percent of the companies that deal with more than one of the public Cloud providers. And while many of them have a preferred vendor, they basically want to ensure that they’re independent of a specific vendor. And hence when it comes to strategy, And how you basically create an overview and your governance processes. I mean, it’s very important that you keep a multicolored strategy in mind because that’s basically what’s happening in almost every large company.
Key challenges around Cloud native is that it’s a fairly radical paradigm shift. So companies struggle with basic adopting, some of the new paradigms around consequent utilization Ation of cloud services and the shift over to microservice architectures. The reason is that in part is an educational one, you need to train your people. I’m in part. It’s also a governance and compliance issue where companies don’t have the infrastructure to actually understand what do I have in the cloud and what is the security issues that come up? Who is actually responsible for what part of the cloud. So many of these questions need to be answered as part of that transition.
From traditional on-premise architectures over to a true native Cloud approach. But it’s key for your Cloud native roadmap that you have a full understanding, what that means. So it has aspects of organizational change in the transformations of, of the way that you actually develop and deploy software. But it’s also of key importance that you Don’t forget about the infrastructure that allows you to guide and govern the processes. So questions around compliance and security and that can how to ensure that as part of your Cloud transformation that actually, is what happens is of key importance. That’s an area where we at Lennox provide very good Solutions. So if you
Cloud strategy, and you’re wondering how to govern and how to ensure compliance with that move into the cloud. And how to understand, who owns, what in the cloud. And also, you could possibly need help with some of the security questions.