Cloud Computing For Dummies Read A Chapter
Chapter 12 Using Software as a Service
In This Chapter
▶ Looking at the origins of SaaS: Salesforce.com
▶ Understanding how the SaaS model works
▶ Understanding the economics and the ecosystem
"When did Software as a Service get its start?" might sound like a straightforward question, but it isn't. In one way, you could say that when timesharing systems were all the rage more than 30 years ago, all software was delivered to customers as a service. Mainframe systems were simply too expensive for most companies to buy their own systems. A couple of decades later, minicomputers, servers, and personal computers changed the dynamics of the market. Economically, it was feasible for any Tom, Dick, and Harriet to own their own systems and the software. Not all software moved to an internal model however. (Software such as ADP's payroll system, for example, remained Software as a Service.)
Two key events converged to create the model that we now call Software as a Service (SaaS):
✓ First, the Internet became a commercial platform.
✓ Second, software costs and complexities became so difficult that running, upgrading, and managing software become too complex for many companies to manage. This was especially true for small- and mediumsized companies that didn't want the expenses of managingall the components. These companies were the first to embrace this new generation of SaaS. Today, SaaS is the most mature area of cloud computing. SaaS gained initial traction with the customer relationship management (CRM) market and has expanded into others - particularly the collaboration market and the enabling tools and management environments. In this chapter, we explain what SaaS is, talk about its business model, and discuss the types of vendors that are in the market today.
Definition of Cloud Computing
Cloud Computing is the next stage in evolution of the internet. The cloud in cloud computing provides the means through which everything - from computing power to computing infrastructure, applications, business processes to personnal collaboration - can be delivered to you as a service wherever and whenever you need.
Book Review
Cloud computing for dummies
It was inevitable - a "Dummies" book for the cloud
By Jon Brodkin on Mon, 11/30/09 - 6:14pm. 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."