10 mitos tentang Cloud
By David Mitchell Smith
Cloud computing, even with its maturity in the past decade and use by businesses, is still prone to a good deal of myth surrounding its real value. Whether they revolve around security concerns or cost savings, cloud myths primarily serve to impede innovation and distract us from real progress.
Check out the following myths and consider whether your perception is closer to reality or if you’re living in your own cloud of dangerous assumptions. Then review our advice for how to take advantage of the truth.
Myth 1: Cloud Is Always About MoneySometimes the cloud saves money, but there are many other reasons cited for migrating to the cloud, the most common of which is for agility. Gartner’s 2014 CIO survey shows that cost savings account for only 14% of the reasons for organizations’ use of the public cloud. Saving money may end up one of the benefits, but it should not be taken for granted.
Advice: Don’t assume you will save money unless you have done the hard work of honestly analyzing the situation. Utilize total cost of ownership and other models on a case-by-case basis and assess the implications of moving from capital expenditure (capex) to operating expenditure (opex). But most importantly, look beyond pure financial issues.
Myth 2: You Have to Be Cloud to Be GoodSome vendors practice “cloud washing” — the tendency to call things cloud whether they are or not. While some cloud washing is accidental and a result of legitimate confusion, we also see IT organizations call many things cloud as part of their efforts to gain funding and meet nebulous cloud demands and strategies.
Advice: Call things what they are. Many other capabilities (e.g., automation, virtualization) and characteristics can be good and do not need to be cloud washed.
Myth 3: Cloud Should Be Used for EverythingUnless there are cost savings, moving a legacy application that doesn’t change is not a good candidate. The cloud fits best where value is placed on flexibility and the business has the ability to consume and pay for only what is needed when needed.
Advice: The cloud may not benefit all workloads equally. Don’t be afraid to propose noncloud solutions when appropriate.
Myth 4: “The CEO Said So” Is a Cloud StrategyWhen asked about what their cloud strategy is, many companies don’t have one and the default is often (stated or not) that they are just doing what their CEO wants.
Advice: A cloud strategy begins by identifying business goals and mapping potential benefits of the cloud to them, while mitigating the potential drawbacks. Cloud should be thought of as a means to an end. The end must be specified first.
Myth 5: We Need One Cloud Strategy or VendorCloud computing is not one thing and a cloud strategy has to be based on this reality.
Advice: A cloud strategy should be based on aligning business goals with potential benefits. A single cloud strategy makes sense if it makes use of a decision framework that allows for and expects multiple answers.
Myth 6: Cloud Is Less Secure Than On-Premises CapabilitiesCloud computing is perceived as less secure. To date, there have been very few security breaches in the public cloud — most breaches continue to involve on-premises data center environments.
Advice: Don’t assume that cloud providers are not secure, but also don’t assume they are. Cloud providers should have to demonstrate their capabilities, but once they have done so there is no reason to believe their offerings cannot be secure.
Myth 7: Cloud Is Not for Mission-Critical UseCloud computing is not all or nothing. It is being adopted (and should be adopted) in steps and in specific cases.
Advice: Mission-critical can mean different things. If it means complex systems, approaches such as taking a phased approach can ease the movement to the cloud. Hybrid solutions can also play a key role.
Myth 8: Cloud = Data CenterMost cloud decisions are not (and should not be) about completely shutting down data centers and moving everything to the cloud. In general, data center outsourcing, data center modernization and data center strategies are related to, but not synonymous with the cloud.
Advice: Look at cloud decisions on a workload-by-workload basis, rather than taking an all-or-nothing approach.
Myth 9: Migrating to the Cloud Means You Automatically Get All Cloud CharacteristicsCloud computing has unique attributes and characteristics. Many migrations to the cloud are “lift and shift” rehosting, or other movements that do not offer scalability and elasticity. Other types of cloud migration (refactoring and rewriting, for example) offer more characteristics. The most common use case for the cloud, however, is new applications.
Advice: Distinguish between applications hosted in the cloud from cloud services. There are “half steps” to the cloud that have some benefits (there is no need to buy hardware, for example) and these can be valuable. However, they do not provide the same outcomes.
Myth 10: Virtualization = Private CloudVirtualization is a commonly used enabling technology for cloud computing. However, it is not the only way to implement cloud computing. Not only is it not necessary, it is not sufficient either.
Advice: Use the right term to describe what you are building. You don’t have to be cloud to be good. Avoid mis-setting expectations and adding to cloud confusion.
David Mitchell Smith is a vice president and Gartner Fellow in Gartner Research, where he leads the agenda for cloud computing and specializes in the impact of catalytic technologies such as the Internet, Web technologies, and consumer technologies.
This article was written by Gartner Inc. from Forbes and was legally licensed through the NewsCred publisher network