UNLIMITED
Cool Vendor That Does Not Exist Yet "AI Core Technologies": Cool Vendor That Does Not Exist Yet: Ideas for vendors that the world needs but doesn't have yet. Analysts meld predictions, research community musings, and other resources to deliver ideas that venture capitalists would do well to listen to. by TechWave: A Gartner Podcast for IT Leadersratings:
Length:
29 minutes
Released:
May 11, 2022
Format:
Podcast episode
Description
Worldwide, public cloud services are forecast to grow by 20.4% (22.0% in constant currency) in 2022. Organizations continue to accelerate cloud adoption, which is driving a five-year compound annual growth rate of 19.6% (19.4% in constant currency). The continued growth of cloud quite naturally leads to a discussion about some of the primary providers, often referred to in the market as the hyperscale vendors. Examples of hyperscale vendors include Amazon Web Services (AWS), Microsoft Azure, Google Cloud Platform (GCP) and Alibaba’s Alicloud. Others may also be considering services from Facebook or Apple.A hyperscale vendor is a very large-scale cloud provider with global reach and impact. The potential for a hyperscale cloud provider’s failure is a classic high-impact/low-frequency risk. More specifically, “concentration” risk focuses on the level of dependency (reliance) an organization’s business, processes and data may lie with a specific vendor’s offerings and services. Understanding the scope and scale of cloud service provider failure is critical in order to take steps to manage risk.Cloud services democratize access to resilience and redundancy capabilities previously only cost-effectively available to the largest enterprises. However, it is your responsibility to take advantage of these capabilities through resilient design that places the emphasis upon avoiding disasters rather than recovering from disasters. As organizations embrace cloud capabilities, the most effective teams strive to avoid service interruptions by creating systems that are highly available. This allows them to sidestep failures in underlying systems and continue operating with minimal impact to users, rather than recovering from an outage.Traditional disaster recovery (DR) thinking is rooted in the failure of physical data centers. However, in public cloud infrastructure and platform as a service (IaaS and PaaS), the failures with broad customer impact are rarely rooted in the data center issues. Rather, they are the result of software bugs that cause one or more cloud services to fail.IT leaders should rethink traditional disaster recovery architectures in favor of more effective resiliency patterns — not only when deploying new applications in public cloud IaaS or PaaS, but also when migrating existing applications to public cloud environments.
Released:
May 11, 2022
Format:
Podcast episode
Titles in the series (43)
- 33 min listen