Many enterprises are investing more in public cloud, and for good reason. The public cloud offers unparalleled scale and agility; enterprises can quickly deploy new projects without infrastructure investments and spin up or tear down workloads as needed. Indeed, many organisations now have a “cloud-first” policy: data and applications are deployed to the public cloud unless there’s a good reason not to. With the infrastructure looked after elsewhere, IT teams are freed up to work on more creative and innovative activities.
At the same time, though, private cloud is growing apace too. As regulations bite and fines for non-compliance and security breaches stack up, many organisations simply cannot legally put sensitive data in the public cloud, while others fear the lack of control and possible security implications that handing data into the care of a third party entails. But the decision on where to run applications is not just about control and security, cost is a major consideration. With the appropriate technology, which mimics that of the major public cloud providers, it is possible to run private clouds at significantly lower cost compared to public clouds.
Because of this, a hybrid cloud setup is a popular option, with mission-critical applications, sensitive data and predictable workloads kept on premises, while commodity workloads, non-sensitive data and transient workloads are moved off into the public cloud.
But who should make the decisions about where data and applications are deployed, and on what criteria should they be based? The self-service ethos which is part and parcel of the cloud computing model has changed the way such decisions are made.
During this web seminar our expert panellists will be investigating the factors that all organisations need to consider when pursuing a cloud-first or hybrid cloud strategy, including price, latency, vendor lock-in. We will also be looking at whether such decisions still rest with IT or if other lines-of-business are now taking the lead in cloud decisions, and if so what the implications are for data governance, security and compliance.