If you’re struggling to learn about cloud computing and evaluate the risks and benefits it brings to your IT operation, there is a new book for you – titled, of course, “Cloud Computing for Dummies.”
Written by an experienced team of technology analysts from Hurwitz & Associates (which has also written “Dummies” books on service-oriented architecture, collaboration and other IT topics), the 300-page volume covers the basic types of cloud computing services and offers insight into how to manage and plan cloud deployments. The book is aimed both at businesspeople who want little or nothing to do with technology, and at IT professionals who are knowledgeable yet new to the cloud.
“We think that cloud computing, in all its forms, is transforming the computing landscape,” the authors write. “It will change the way we deploy technology and how we think about the economics of computing.”
If you’re interested in getting a copy, the book is available from Amazon and other book sellers.
Rather than review the whole book, I’ll just quote a few passages from Cloud Computing for Dummies to give you a sense of what it’s all about.
In the first chapter “Grasping the Fundamentals,” the authors note “While there are a lot of technical considerations, keep in mind the fundamental truth: Cloud computing is a business and economic model. Is cloud computing a replacement for the traditional data center? The answer is complicated. In some cases, yes; in some cases, no.”
Definitions of cloud computing vary, so the Hurwitz team offers its own definition, saying “the cloud itself is a set of hardware, networks, storage, services, and interfaces that enable the delivery of computing as a service. Cloud services include the delivery of software, infrastructure, and storage over the Internet (either as separate components or a complete platform) based on user demand.”
Management and security is covered, with Hurwitz recommending that customers ask questions such as “Where does your data physically live? Do you have the cloud provider’s assurance that it will remain private? Does your cloud provider separate (partition) your data, applications and/or management tools from other users of its cloud services? Are there clear penalties for a data or system breach? Does the cloud provider have application level firewalls and other tools that help keep your application or code safe?”
The burden is on the customer to vet the cloud provider beforehand. A cloud vendor’s “security approach may conflict with your company’s rules,” Hurwitz notes. “No governance body will accept the excuse that you simply didn’t know how your provider protected your information.”
The book concludes with some general tips, such as “Don’t forget about business process. Start with the business process that you want to automate with your cloud initiatives. No matter which form of cloud you’re considering, process is the building block. If you haven’t figured out how business processes will be managed in this new distributed world, your business could be at risk.”
Hurwitz also cautions “Don’t apply the cloud to everything. Not everything belongs in a cloud. For example your data center might have a large, complex, and customized application used by a dozen people. It’s critical to your business. You have no economic or business reason to move that application to the cloud. Do your homework so you have guidelines to help you determine if an application or a function belongs in the data center, a public cloud, or a private cloud.”
Jon Brodkin writes about Microsoft, Google, browsers, operating systems, PCs, mobile devices, cloud computing, virtualization, open source and a bunch of other tech stuff for Network World. He also cares just a little bit too much about Boston sports teams. Follow Jon on Twitter @jbrodkin.
Policy on comments: Respectful discussion is welcomed! However, comments that use inappropriate language, consist of name calling or personal attacks, or include accusations of wrongdoing are not appropriate. Those comments will be deleted or edited.