Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Cloud Computing For Dummies

Cloud Computing For Dummies

Move the right workloads to the cloud without losing control of costs, data, or future choices.
by Judith Hurwitz 2009 336 pages
3.40
134 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Cloud computing is a business model for elastic, metered services, not remote hosting

More than remote hosting. Cloud computing delivers computing resources as services, so organizations can request capacity, applications, or storage when needed instead of buying and maintaining every component themselves. Its promise is as much economic and organizational as technical: faster access to resources can help a business respond to changing demand without waiting for internal procurement and setup.

Four operating traits. The book identifies elasticity, self-service provisioning, application programming interfaces, and metered, pay-as-you-go use as defining features. A cloud should also provide security and service management, including performance monitoring. A CEO in the book asks why the company’s IT department cannot provide resources as quickly as Amazon. The CIO’s answer is that some work fits, such as testing and email, while unique, sensitive applications may not.

Analysis

The useful shift is from asking where a server sits to asking how quickly a business can obtain a dependable capability. That makes cloud a question of operating design, not merely infrastructure sourcing. The analogy to a utility is helpful, but it can obscure that computing services are not interchangeable commodities: security, integration, and service quality differ. The book’s insistence on business context prevents the utility metaphor from turning into a blanket argument for outsourcing.

Rent the cloud layer that removes your actual bottleneck

Three service layers. Infrastructure as a Service, or IaaS, rents computing, storage, and networking resources. Platform as a Service, or PaaS, adds a development and deployment environment. Software as a Service, or SaaS, delivers a finished application, such as customer relationship management or email. These are useful distinctions, not sealed compartments: a provider can combine layers.

Match layer to need. A research team needing temporary computing power may use IaaS. Developers building a new application may prefer PaaS, which supplies tools and a runtime environment. A company seeking sales software without maintaining its own servers may choose SaaS. The convenience has tradeoffs. A PaaS platform can tie an application to a vendor’s proprietary tools, while SaaS still requires data integration, configuration, and support planning.

Analysis

The three layers clarify who manages which parts of the technology, and therefore who carries the work and risk. They also expose a common procurement mistake: choosing a familiar product category before defining the problem. A finished application can reduce operational burden, while infrastructure rental preserves more technical control but demands more expertise. The right comparison is not simply flexibility versus convenience. It is whether the organization wants to manage the layer it is renting.

Package workloads as independent services before moving them between environments

Define the workload. A workload is an independent service, or a collection of code, that can run without relying on hidden external elements. It might be a whole application or one reusable function. The book distinguishes batch work, which can run later, from real-time work, such as calculating tax during an online purchase. Each type has different timing and reliability needs.

Make connections explicit. A workload placed in a container with a defined interface is easier to test, reuse, and move. Intuit, for example, built a payment function that partners could use rather than write themselves. But independent pieces still need orchestration: an online sale may connect sales, credit checks, inventory, and shipping. Test the full business process, not just each component.

Analysis

This is the architectural hinge between cloud flexibility and real-world reliability. A service that looks portable in isolation may fail when its data, timing assumptions, or dependent systems are considered. The book’s container idea is strongest when treated as a contract: each component has a clear job, and its dependencies are visible. Modularity is not a magic solvent for complexity. It makes complexity easier to locate, test, and change.

Cloud costs fall when providers repeat a few workloads at massive scale

Scale depends on sameness. The book contrasts mixed corporate data centers with cloud centers built for a small number of standardized workloads. A surveyed large traditional data center cost roughly $10 million to $25 million annually, with 58 percent attributed to labor, property, heating, and cooling. In the cloud-center estimates discussed, labor was 6 percent of operating costs. The figures come from specific historical sources, not a universal price list.

Simpler operations compound. The text compares staffing ratios of about one operations employee per 65 servers in corporate centers with one per 850 servers in cloud centers. Standard hardware, software, and management practices make that efficiency possible. A company running hundreds of unlike applications cannot automatically reproduce those economics. If a workload is already efficient internally or requires extensive customization, the cloud may cost more.

Analysis

The memorable insight is that scale comes from reducing variation, not simply accumulating machines. This resembles a manufacturing line: repetition permits specialized processes and tighter cost control. But the same specialization narrows what the system handles well. Enterprise data centers support diverse, sometimes irreplaceable work; a cloud provider’s efficiency may depend on refusing that diversity. Cost comparisons therefore need to examine workload fit, not just provider size or headline rates.

Keep responsibility for your data even after a provider takes custody

Track the data lifecycle. Data is created, changed, secured, stored, and eventually destroyed. A cloud provider may operate the systems, but the organization remains responsible for protecting its information and meeting applicable rules. The book highlights three questions: where data is located, who controls it, and how it is protected while moving. A provider’s distributed infrastructure can make geographic location difficult to identify, even as national laws differ.

Ask beyond encryption. Review access controls, audit records, backup and recovery, data ownership, permitted secondary uses, and proof of secure deletion. A company moving patient or financial information must check relevant compliance requirements; moving it to an outside service does not remove them. Also ask how data will be returned at contract termination and what happens if the provider fails. Metadata, the definitions that give data meaning, must remain consistent across systems.

Analysis

The distinction between custody and responsibility is crucial. Outsourcing storage changes who operates the equipment, not who bears the consequences of mishandled records. Data location, deletion, and portability are also governance questions disguised as technical details. The book’s checklist encourages customers to make implicit assumptions explicit in contracts and controls. Encryption matters, but it cannot by itself answer who can use data, interpret it, recover it, or prove that it is gone.

Treat service agreements as measurable promises, not reassurance

Specify the service. A service-level agreement, or SLA, is a contract describing the service a provider must deliver and the consequences of falling short. It should fit the business importance of the workload. A monthly research report may tolerate downtime that would be unacceptable for a real-time security system. The book warns that a provider’s standard agreement may protect the provider more than the customer.

Verify performance yourself. Track availability, response time, support, provisioning, security, and billing. A polished dashboard is not a substitute for independent monitoring. In a hybrid environment, a failure may sit with the application provider, its infrastructure vendor, or the connection between them. Clarify who diagnoses and fixes each kind of incident, and how planned maintenance affects uptime calculations. If a provider cannot meet a critical service requirement, the cloud is not the right choice for that workload.

Analysis

An SLA translates trust into an observable relationship, but only if its measurements reflect the outcome the business cares about. A server can be technically available while a customer-facing process remains broken. This is why the book emphasizes service-level monitoring across connected systems rather than treating infrastructure uptime as the whole story. Contracts also have limits: a credit for downtime may not compensate for lost revenue, damaged trust, or compliance failures.

Choose public, private, or hybrid clouds according to control and workload

Control comes in degrees. A public cloud serves customers through a provider’s shared environment. A private cloud brings cloud features, such as self-service and elastic resource allocation, into an environment dedicated to one organization, often behind its firewall. A hybrid approach combines public and private services with traditional systems. The book expects many organizations to use a mixture rather than force every application into one model.

Fit the environment to the work. A standardized email service, temporary test capacity, or collaboration project may suit a public cloud. Sensitive information, strict data-location rules, or critical performance needs may favor private resources. A retailer might accept public access for customer requests while keeping customer records in a controlled private environment. Hybrid management is more complicated, however, because services must work together and be governed consistently.

Analysis

The public-private distinction is best understood as a choice about control, not a simple ranking of safety. A private cloud gives an organization more direct oversight, but it also inherits the cost and operational responsibility of running the environment. A public provider may have greater scale and specialized capabilities. The hybrid model preserves choice, yet introduces coordination work. Each boundary between systems becomes a potential point of failure, cost, or confusion.

Compare recoverable costs, not cloud fees against hardware prices

Count the full cost. The book names its application cost model Total Cost of Application Ownership, or TCAO. It includes servers, storage, networking, backup, disaster recovery, facility costs, platforms, software maintenance, help desk, operations staff, and management tools. Then adjust for costs that will actually disappear if the application moves. Removing a few servers may not reduce rent, staffing, or network expenses.

Use scenarios carefully. The book compares a $100,000 software purchase plus 20 percent annual maintenance, totaling about $200,000 over five years, with a SaaS example for 50 users at $150 per user monthly, totaling $37,500 over that period. This illustrates a possible advantage, not a guaranteed saving. Integration, migration, service levels, compliance, and data-center capacity can change the result. Recalculate as prices, workloads, and business needs change.

Analysis

The most important accounting distinction is between allocated cost and avoidable cost. A spreadsheet can assign a slice of cooling or staff time to an application, but those expenses may remain after migration. The TCAO framework forces a more realistic comparison by including operations and risk. Its limitation is practical: measuring every cost precisely can itself consume effort. The goal is not perfect accounting, but decisions that do not confuse a lower invoice with a lower total cost.

Demand portable interfaces before convenience turns into vendor lock-in

Separate two freedoms. Interoperability means services or applications can work together across environments. Portability means an application, virtual machine, or data can move from one provider to another without major rework. Both depend on interfaces, formats, and standards. If each provider uses proprietary APIs or data structures, a convenient first choice can become an expensive long-term commitment.

Check before committing. Ask how data and applications can be exported, what will need rewriting, and whether the provider supports relevant standards. The book cites the Open Virtualization Format as an effort to package virtual machines so they can be used across different environments. Standards do not guarantee easy migration, and an agreed specification is useful only when it is actually implemented. Build portability into the architecture and contract before switching providers becomes urgent.

Analysis

Portability has option value: it preserves the ability to respond if prices, service quality, or strategy change. That option is easiest to protect before an application accumulates provider-specific dependencies. Yet openness is not free. A standardized interface may constrain specialized features, and moving a complex system still requires testing and data conversion. The practical aim is not to eliminate every dependency, but to know which dependencies are deliberate and what escaping them would cost.

Start with a pilot that proves value without risking the whole business

Choose a bounded experiment. The book recommends starting with a pilot rather than reacting to cost pressure by moving everything. Testing and development are promising candidates because their resource needs are temporary and may peak unpredictably. A company can also try overflow computing for a marketing campaign or evaluate a new application as a service before committing to it.

Plan for people, too. Assess risks across people, processes, and technology. Explain why the change is happening, train staff on new tools, and involve the teams whose work will change. A pilot should test more than whether the software runs: it should reveal integration effort, support quality, data handling, costs, and the ability to monitor the provider. A small success can build confidence; a poorly scoped experiment can create new silos or surprise bills.

Analysis

A pilot is valuable because it converts abstract debate into evidence, while limiting the cost of being wrong. The strongest experiments have a clear business question and criteria for success, rather than serving as demonstrations that cloud technology exists. The human side is not soft overhead: unfamiliar processes and threatened roles can undermine a technically sound deployment. A pilot should therefore test the organization’s ability to operate the service, not merely the provider’s ability to supply it.

Analysis

This book is best read as an early map of a shift in how organizations buy and organize computing, not as a current vendor directory. Its durable argument is that cloud value emerges when technical design, operating responsibility, and business economics align. Elastic capacity matters because it changes the timing of investment. Standardized services matter because they make resources reusable. Scale matters because repeatable workloads can be operated more cheaply. Each advantage depends on conditions that can be undermined by poor architecture, unpredictable demand, or expensive governance requirements.

The book’s strongest corrective is its refusal to equate outsourcing with abdication. A provider may run the infrastructure, but the customer still owns decisions about data, compliance, service continuity, and acceptable risk. This is more than a security warning. It is a general lesson about delegated systems: responsibility should follow the consequences of failure, not merely the location of the work. SLAs, monitoring, service catalogs, and governance bodies are mechanisms for preserving that responsibility across organizational boundaries.

Its economic reasoning is also more subtle than the familiar claim that renting is cheaper than owning. Cloud providers gain efficiency through standardization and scale, but the customer’s savings depend on actual cost reduction, not allocated costs that remain after migration. Applications with unusual requirements or costly dependencies may be better left in a traditional environment. A private cloud can improve utilization and service speed, yet does not acquire public-cloud economics automatically. The strongest decision process therefore evaluates workload fit, migration costs, risk, and future flexibility together.

The book was published during cloud computing’s early commercial phase, so its product examples and forecasts are historical. Its conceptual structure remains useful: distinguish infrastructure, platforms, and applications; treat workloads as designed services; and ask how systems can be governed across public, private, and internal environments. The central question is not whether an organization should move to the cloud. It is which capabilities belong there, under what terms, and with what evidence that the arrangement serves the business.

Summary in 30 Seconds
Cloud services provide elastic capacity, self-service access, and usage-based billing, but their value depends on workload fit and operational scale. Match rented infrastructure, development platforms, or finished applications to the need. Compare total costs that actually disappear with migration, integration, and compliance expenses. Providers may manage systems, but organizations remain accountable for data, security, and service continuity. Test with a limited pilot, measure performance independently, and require practical ways to move data and applications later.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.40 out of 5
Average of 134 ratings from Goodreads and Amazon.

Cloud Computing For Dummies receives mixed reviews, with an average rating of 3.42 out of 5. Readers appreciate its comprehensive yet simple approach to explaining cloud computing concepts, particularly for beginners and non-technical professionals. The book covers various aspects including technology, business impact, and implementation strategies. Some readers find it repetitive and overly focused on business aspects rather than technical details. Critics note potential bias and outdated information in earlier editions. Overall, it's considered a good starting point for those new to cloud computing, though more advanced readers may find it lacking depth.

Your rating:
4.04
99 ratings
Want to read the full book?

Glossary

Elasticity

Capacity that expands or contracts

The ability to increase or reduce computing resources as demand changes. In a cloud environment, users can obtain additional processing, storage, or other resources and release them when no longer needed. Elasticity helps avoid building every system around peak demand, though the actual scaling process may require a user request or depend on provider limits.

Infrastructure as a Service

Rented computing infrastructure

A cloud service model that provides computing resources such as servers, storage, networking, and data-center capacity for use by customers. Customers rent rather than purchase and install the infrastructure, often paying according to usage. The provider may also supply operating systems and virtualization, while the customer manages applications and some of the environment.

Platform as a Service

Cloud application development platform

A cloud service model that provides developers with a platform for building, deploying, and managing applications. It can include development tools, runtime software, databases, testing, and deployment capabilities. PaaS reduces the need to manage underlying infrastructure, but proprietary tools or components can make applications difficult to move to another platform.

Software as a Service

Provider-hosted application

A model in which a provider hosts and operates an application that customers access as a service, commonly through the Internet. Customers typically pay recurring fees based on users or usage rather than purchasing and maintaining the complete software and infrastructure themselves. The customer still needs to consider data integration, configuration, security, and service quality.

Multi-tenancy

Shared system, separated customers

An architecture in which a provider serves multiple customer organizations using shared underlying resources. The application is designed to keep each customer’s data, access, and configuration separate. Multi-tenancy can improve provider efficiency and reduce costs, but customers need assurance that separation and access controls work correctly.

Workload

Independent executable service

A workload is an independent service or collection of code that can be executed, ranging from a small function to a complete application. Cloud workloads should have clear purposes, documented interfaces, and understood dependencies. They may run in batch mode or require real-time responses, and those differences affect their performance and service requirements.

Service oriented architecture

Reusable, loosely linked software services

An approach to building business applications from software components that provide defined services through standardized interfaces. The components are loosely coupled, meaning they can interact without extensive dependencies on one another. This makes them easier to reuse, combine, and change, and can help organizations connect internal systems with cloud services.

Total Cost of Application Ownership

Full annual application cost

The book’s cost model for comparing an application’s data-center expenses with a cloud alternative. It includes hardware, storage, networking, backup, disaster recovery, facilities, platform and software maintenance, help-desk support, operations staff, and management software. The model also requires adjusting for which costs would actually be eliminated after migration.

Trusted cloud

Secure, transparent, evidenced service

A cloud service environment that is secure, makes its controls and results visible to customers, and can provide evidence that it delivers the promised service. The concept responds to customers’ concern that they cannot directly inspect all provider infrastructure. Trust depends on demonstrable operations, not solely on provider assurances.

About the Author

Judith Hurwitz is an experienced technology consultant, author, and speaker specializing in emerging technologies. As the president and CEO of Hurwitz & Associates, she has been at the forefront of the software industry for over 30 years. Judith Hurwitz has authored numerous books on technology topics, including cloud computing, service-oriented architecture, and artificial intelligence. Her expertise in translating complex technical concepts into accessible language for business leaders has made her a sought-after consultant and speaker. Hurwitz's work focuses on helping organizations understand and implement emerging technologies to drive business value and innovation.

Download PDF

To save this Cloud Computing For Dummies summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.36 MB     Pages: 17

Download EPUB

To read this Cloud Computing For Dummies summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.46 MB     Pages: 20
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...