Category: Cloud
“Cloud is about how you do computing, not where you do computing.”, rightly said by Paul Maritz, CEO of VMWare
The corona virus quarantine has made a lot of organisations across various industries establish remote operations and not all companies are able to handle the forced move to a virtual office. Before the impact of the Corona virus, only 62* percent of the workloads were in the Cloud but as per 87 percent of the IT decision makers, 95 percent of the workload will be in the Cloud by 2025. This acceleration was fuelled by Covid-19 acting as a catalyst for cloud migration.
The current state of remote work was largely unforeseen, no disaster recovery plan included anything for a mass outbreak of a virus. This transition to remote work on such a massive scale would not have been possible in the server-led infrastructure 15 to 20 years ago. Large enterprises can now deliver new services 30 to 60** percent faster through cloud migration. After several months into quarantine, organisations have started refining and optimising workloads into the Cloud. When and how businesses will be able to resume on-premise activities at the office remains a big question.
The cost of cloud migration was one of the major reasons for many companies to not migrate to the Cloud. But, the current circumstances have led some of the organisations around the globe to renew their efforts to get into the public cloud. It is time one stops thinking about everything being a corporate owned machine, in a corporate office, rather utilise the opportunity to focus on virtualisation of servers, storage and networks. At this crisis time, virtualisation needs to be brought to end-user devices and Mobile Device Management has to be something every company needs to think about.
Though corporate IT resources are built to offer high levels of security, quarantines mean that direct, in-person access to them is limited if not completely unavailable. Enterprises considering digital transformation prior to the pandemic might have only wanted to move up to 30-40*** percent of their existing infrastructure to the public cloud. But now, more than 70** percent of executives have indicated a belief that cloud will help them innovate faster while reducing implementation and operational risks.
Long term plans for organizations may include use of public cloud, mobile computing, and moving to 5G wireless network. This allows companies to operate anytime and anywhere, which is much easier for born-in-the-cloud companies. Large enterprises cannot move nimbly, but the circumstances have shown the need for rapid changes beyond static systems with datacentres. Organisations that embrace flexibility will be able to recover faster than their competitors.
The entire process from start to finish, requires significant changes and change management with how an organisation’s teams interact, process and share their data amongst each other. The sweeping global transition to remote work has seen virtual collaboration tools thrown into the spotlight of economic activity and their demand has sky-rocketed.
“Beyond the emergency action needed at the start of the pandemic, many organizations have turned to mitigating risk through flexibility of infrastructure”, says David Linthicum, chief cloud strategy officer with audit and consulting advisor Deloitte.
While cloud adoption offers a powerful opportunity to unlock business value, there remains a distinguishable hesitation around a few challenges of this transition. Cybersecurity is the biggest concern and remains a significant barrier when companies think of migrating to the cloud. Security threats have increased substantially during Covid-19, and organisations need to recognise and respond. Advanced cybersecurity solutions are now available which can help boost the security architecture.
Cloud computing, which has been touted for its flexibility, reliability and security, has emerged as one of the few saving graces for businesses during this pandemic. Its use is critical for companies to maintain operations, but even more critical for their ability to continue to service their customers.
Cloud adaptation provides an avenue of growth which can help balance the economic challenges faced by various organizations. Cloud budgets today account for approximately 5** percent of the average IT budgets, a figure that is likely to double by 2023.
As organisations have started adjusting to the new reality of the pandemic, cloud adoption represents a multi-billion-dollar opportunity for businesses in every region of the world. The world will eventually emerge from this period of remote work, but the way we do business will be transformed forever.
References:
*Sead Fadilpasic : Cloud migration set for major rise following pandemic, June’20. Retrieved from ITProPortal
**Luv Grimond and Alain Schneuwly : Accelerating Cloud Adoption After Pandemic, June’20. Retrieved from Jakarta Globe
***Joao-Pierre S. Ruth : Next Steps for Cloud Infrastructure Beyond the Pandemic, April’20. Retrieved from Information Week
Not to name names, but I’ve been reading in several publications that one of the main reasons to go to multicloud is to avoid vendor lock-in. While I can see the logic behind this assumption—that having more cloud providers means you can be more independent—the reality is much different.
For example, if you have an application in the cloud, and you’re using a multicloud architecture, you’ll have two or three choices where to place that application workload and associated data: Amazon Web Services, Microsoft Azure, and/or Google Cloud Platform.
You’ll pick one cloud for that application and do the standard migration processes to get it up and running. What most people don’t understand is that, as part of that migration, you’re likely to make the application workloads cloud-native. That means you’re going to alter the applications, slightly or heavily, to take advantage of the native cloud services, such as API management, governance, security, and storage.
By altering the application to be cloud-native, you’re locking yourself in to that cloud provider, for that application. If you don’t go the cloud-native approach, it’ll be easier to migrate that applocation to a different provider later—but at the price of a suboptimal deployment due to not being cloud-native.
You have to make a trade-off between using advanced application capabilities (cloud-native), and thus also accepting vendor lockin, or keeping the app geberic and less optimal to avoid that lockin. It does not matter if you’re using a single-cloud architecture or a multicloud architecture, the lockin trade-off is the same.
In this 60-second video, learn how the cloud-native approach is changing the way enterprises structure their technologies, from Craig McLuckie, founder and CEO of Heptio, and one of the inventors of open-source system Kubernetes.
IT INSIGHTS
What is the cloud-native approach?
Of course, it is an advantage to have another public cloud connected and integrated into your architecture so that other public cloud options are available if and when needed. But you still have to make that same trade-off between being cloud-native and avoiding lockin.
You might think you can avoid the trade-off by using containers or otherwise writing applications so they are portable. But there is a trade-off there as well. Containers are great, and they do provide cloud-to-cloud portability, but you’ll have to modify most applications to take full advantage of containers. That could be an even bigger cost than going cloud-native. Is it worth the avoided lockin? That’s a question you’ll need to answer for each case.
Moreover, writing applications so they are portable typically leads to the least-common-denominator approach to be able to work with all platforms. And that means that they will not work well everywhere, because they are not cloud-native. I suppose you could write portable applications that are cloud-native to multiple clouds, but then you’re really writing the application multiple times in advance and just using one instance at a time. That’s really complex and expensive.
Lockin is unavoidable. But lockin is a choice we all must make in several areas: language, tooling, architecture, and, yes, platform. The key is to choose each lockin poont wisely, to mimimize the need to change horses. But when a change must happen, there’ll be a price to be paid. If you make the right choices, you’ll pay that price not very often, and you”ll have gained more from those choices in the meantime than you would have gained from a least-common-denominator approach