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

Cloud Computing

Choose cloud services that fit your workload, budget, and risk, before convenience sets the terms.
by Nayan B. Ruparelia 2016 278 pages
3.31
159 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat cloud computing as a service model, not a synonym for remote servers

Cloud means more than hosting. The book opens with a familiar inefficiency: at peak use, a typical computer may use only about 10 percent of its processor, 60 percent of its memory, and 20 percent of its network capacity. Pooling resources lets users share spare capacity and pay for what they consume instead of buying everything upfront.

Look for the full package. A cloud service must provide broad network access, on-demand self-service, pooled resources, rapid elasticity, and measured usage. Virtualization helps share hardware, but does not by itself provide the portals, orchestration, monitoring, security, and billing that make computing a managed service. If those features are missing, calling a system a cloud does not make it one.

Analysis

The useful distinction is between a technology component and an operating model. Virtual machines can make infrastructure more efficient, but cloud computing also changes how resources are requested, allocated, measured, and paid for. That makes the definition practical: buyers can test a vendor's claims against observable service features instead of accepting a label. The caveat is that the five characteristics describe a model, not a guarantee of quality. A service may be elastic and metered while still being unreliable, costly, or difficult to leave.

Choose the abstraction that removes the work you do not need to own

Buy the right layer. Cloud services range from infrastructure as a service (IaaS), where customers use computing, storage, or networks, to platform as a service (PaaS), which also supplies an operating environment, and software as a service (SaaS), where users simply use a hosted application. The book adds information as a service (INaaS), which delivers useful, contextualized information, and business process as a service (BPaaS), which delivers a business function or workflow.

Separate access from ownership. A cloud can also be public, private, community, or hybrid, describing who can use it and how it is organized. These deployment choices can pair with any service layer. A preinstalled operating system alone does not turn IaaS into PaaS; the provider must supply the platform needed to run applications.

Analysis

The abstraction ladder is really a map of responsibility. Moving upward can free a customer from maintaining more of the technology, but it also gives the provider more influence over how work is performed. That trade is familiar in organizational design: outsourcing routine operations can focus attention on distinctive work, while making the organization more dependent on contracts and interfaces. The important question is not which layer sounds most advanced, but which responsibilities the customer can competently manage and which it can safely delegate.

Assemble reusable cloud cells, then verify how the pieces interoperate

Build from small functions. A cloud cell is a discrete cloud service that performs one technical or business function, such as hosting a database or website. Cells can be reused in larger services rather than rebuilt for every project. A cloud pattern describes a repeatable use case by naming its components, their connections, and the trade-offs involved.

Choose the relationship deliberately. Aggregation combines similar cells, for instance replicas that share demand or support recovery. Composition combines distinct cells, such as storage, a database, and a web server. Federation joins services from separate providers into a composite service. These arrangements can improve speed and reuse, but only if interfaces, data formats, and operating expectations match.

Analysis

This modular view connects cloud design to the broader idea of composability: complex systems become easier to change when their parts have clear boundaries and predictable interfaces. Reuse can reduce duplication, but it also multiplies the consequences of a flawed component. A standard cell may be reused in several settings where it has different security or performance needs. The model is strongest when standardization includes testing and version control, not merely a shared template.

Judge cloud prices by delivered business value, not monthly fees alone

Pricing follows the service. Providers may charge by computing resources consumed, transactions processed, subscriptions, fixed fees, volumes, or service performance. Marketing models include free basic tiers that encourage paid upgrades. These methods can be combined, so a low headline price does not reveal the total cost or the risk transferred to the buyer.

Measure what improves. The book identifies seven sources of cloud value: shifting spending from capital to operations, matching capacity to demand, changing price plans as needs change, reaching markets sooner, working across locations, avoiding excess assets, and improving margins. It illustrates financial checks with payback, return on investment, net present value, and time to market. For example, faster invoice processing matters only to the extent that the extra throughput creates a real business benefit.

Analysis

The central economic insight is that price and value are different questions. Usage billing can reduce the cost of idle capacity, but variable spending can also become hard to predict unless consumption is visible and governed. The book's financial metrics help compare alternatives, yet a spreadsheet cannot make an uncertain benefit certain. Faster processing, for example, has value only if it releases capacity, improves service, or supports additional revenue. A credible business case should expose those assumptions rather than bury them in a single ROI figure.

Contract for the entire data journey, including jurisdiction and recovery

Protect data end to end. Security covers confidentiality, possession, integrity, authenticity, availability, and usefulness, a set known as the Parkerian hexad. Data move through users, applications, networks, storage, backups, and archives, so protections should cover each stage and the links between them. Security containers group systems with shared security requirements, while identification, authentication, and authorization establish who is acting and what they may do.

Make recovery measurable. Agreements should specify availability and recovery needs, including recovery time objective (how quickly service returns) and recovery point objective (how much recent data may be lost). The author recounts losing most of a manuscript when backup software deleted the backup during a failed restore. Redundant disks were not enough; the restore process itself had failed.

Analysis

This section's strongest lesson is that security is a chain of responsibilities, not a feature that can be purchased once. The story of the lost manuscript makes the distinction between having a backup and having a recoverable backup unusually concrete. Resilience engineering similarly asks whether a system can withstand failure and return to operation, not merely whether safeguards exist on paper. Data location adds another layer: legal jurisdiction and ownership should be made explicit, because technical access across borders does not settle who has authority over the information.

Use cloud elasticity where demand swings, not as a universal default

Match capacity to peaks. Elasticity means scaling pooled resources out when demand rises and scaling them back when demand falls. This suits workloads whose needs are irregular: a website can face sudden traffic during a campaign, and video rendering can require substantial computing power only while work is underway. Cloud capacity can help avoid both idle equipment and missed demand.

Check the dependencies. Elasticity does not remove every constraint. A rendering job still needs adequate network bandwidth, and an application may need careful testing to establish how much memory or processing power it requires. The book warns that automatic provisioning can hide the relationship between demand and resource use. Buyers should seek transparent usage and cost reports, and maintain continuity plans for services critical to their business.

Analysis

Elastic capacity is most valuable when demand is uncertain and the cost of being underprepared is meaningful. It resembles an option: the organization pays for access to capacity when needed rather than owning all of it in advance. But an option has conditions. Networks, application design, provider limits, and billing rules can constrain the benefit. The principle is therefore not to maximize elasticity everywhere, but to identify which workloads have variable demand and verify that scaling actually improves the user's experience.

Make cloud migration an integration and governance redesign

Plan the operating model. The book traces a shift from central IT selecting one provider, through arrangements with multiple providers or a service integrator, toward business units choosing approved services from a catalog. In this model, IT increasingly brokers services, sets standards, and oversees risk instead of building every system itself. A cloud maturity model helps assess progress across people, processes, monitoring, governance, and financial management.

Test the connections. Interoperability means being able to use similar services from different providers. It requires more than technical compatibility: security, compliance, data formats, business processes, billing, and reporting must also fit together. The book recommends defining functional, non-functional, and business requirements, then weighting and scoring them to compare options. Cloud adoption is not appropriate for every workload; traditional computing may still fit needs such as especially high performance or resilience.

Analysis

Migration is often described as moving systems, but the deeper change is deciding who can procure technology and who remains accountable for it. A service catalog can make business teams more agile while giving governance a practical place to operate. Interoperability is the hinge: without portable data, compatible processes, and comparable reporting, multiple providers may create fragmentation rather than choice. The model should therefore be evaluated not just by technical readiness, but by whether the organization can coordinate decisions and manage exceptions.

Automate useful workflows around connected devices, not gadgets for their own sake

Connect sensing to service. The Internet of Things links physical devices to networks; an Internet of Services supplies the processes that monitor and support them. The book's Cloud of things and services (CoTS) is a cloud environment that manages connected devices and related services. A sensor-equipped rubbish bin, for example, could report when it is nearly full so a local service can plan collection routes instead of following a fixed schedule.

Turn data into action. Information as a service makes data relevant to a situation, while a business process as a service can organize the steps that act on it. A personal health cloud might gather readings from wearable devices and send an alert when a threshold is reached. These systems can improve coordination, but they also collect sensitive information and require clear rules about access and use.

Analysis

The valuable unit here is not the connected object but the workflow it enables. A sensor matters when its signal changes a decision, such as when a collection crew is dispatched or a clinician is alerted. This is a service-design principle: technology should remove friction from a real task rather than create a new stream of data without a useful response. The same automation can also expose people to monitoring. Efficiency and consent need to be designed together, especially when information concerns health or location.

Treat cloud convenience as a choice about data and power

Infrastructure shapes society. The afterword argues that cheap, centralized computing can make it easier to gather and analyze personal information, influence public opinion, and automate work. The author connects this possibility to the concentration of wealth, citing an increase in the share of US financial assets held by the top 1 percent from 34.6 percent in 2007 to 42.7 percent in 2011. Technology can improve daily life, but those improvements do not by themselves explain or resolve inequality.

Ask who benefits. Cloud services can help a small business reach customers quickly and let people access tools from many devices. The same scale can concentrate information and control in a few organizations. The book's point is not that technology inevitably produces one political outcome, but that convenience should not be used as a substitute for examining ownership, access, privacy, and the distribution of gains.

Analysis

The social argument is strongest when read as a warning about incentives rather than a prediction of inevitable control. Centralized services can make data analysis cheaper and more capable, while also creating efficiencies that smaller organizations could not build alone. Whether the result is broad access or concentrated power depends on governance, competition, labor transitions, and public oversight. The author's discussion usefully resists technological optimism, though the same caution applies to technological pessimism: tools create capacities, while institutions and choices shape how those capacities are used.

Analysis

This book is best understood as a guide to cloud computing as an economic and organizational model, not merely as an account of servers hosted elsewhere. Its central move is to connect technical properties, such as pooled resources and elasticity, to practical questions about contracts, spending, security, and control. That user-centered approach gives the book a coherent thread despite its wide scope, from infrastructure and pricing to personal clouds and political consequences.

Its most useful framework is the ladder of service abstraction. Buyers can distinguish renting infrastructure from using a managed platform, an application, contextual information, or an outsourced process. The cloud-cell idea extends this logic into system design: assemble discrete services, then specify the interfaces and governance that make them work together. The framework is persuasive because it translates a vague technology label into decisions that organizations can test. The book also avoids treating adoption as automatically beneficial. Elasticity can reduce idle capacity, but it can obscure consumption; outsourcing can reduce operational burdens, but it creates dependence; centralized data can enable coordination, but it raises questions of jurisdiction and privacy. Its own account of a failed backup restore gives this caution a human scale: redundancy is not resilience unless recovery works.

The main limitation is that the ideal of interoperability can sound easier than its organizational and commercial reality. Common formats and interfaces do not, by themselves, align incentives, compliance obligations, or service quality. Likewise, the financial case for cloud depends on whether expected benefits can actually be realized, not simply on replacing capital expense with monthly charges. These tensions do not weaken the book's central contribution. They clarify it: cloud adoption is a design choice involving technology, contracts, workflows, and institutional responsibility. The reader's most durable tool is not a preferred vendor or deployment type, but a disciplined way to ask what is being shared, what is being measured, who is accountable, and how the arrangement can fail safely.

Summary in 30 Seconds
Pooling computing resources can reduce idle capacity: a typical computer may use only about 10 percent of its processor at peak use. Choose among infrastructure, platforms, hosted software, and managed processes according to the work you need to own. Compare total cost with measurable business gains, not fees alone. Contracts should define data protection, jurisdiction, availability, and recovery targets. Elasticity suits fluctuating demand, while migration also requires integration, governance, and clear accountability.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.31 out of 5
Average of 159 ratings from Goodreads and Amazon.

The reviews for Cloud Computing are mixed. Some readers found it a helpful introduction to cloud concepts for non-technical audiences, praising its comprehensive coverage and accessibility. Others criticized it for being too basic, outdated, or lacking depth. Many appreciated the broad overview of cloud computing, including business aspects and terminology. However, some technical readers felt it didn't provide enough valuable information. The book seems best suited for beginners or business professionals seeking a high-level understanding of cloud computing, rather than technical experts looking for in-depth knowledge.

Your rating:
4.02
100 ratings
Want to read the full book?

Glossary

Cloud cell

Reusable single-function cloud service

A cloud cell is a discrete cloud service that performs one technical or business function, such as providing storage, a database, or a web server. Cells can be reused as components of larger services. Their value depends on clear interfaces and management practices, so that a cell can be integrated, updated, and tested wherever it is used.

Cloud pattern

Template for a cloud use case

A cloud pattern describes a recurring service or use case through its name, problem, solution, and consequences. The solution identifies the cloud cells involved, their relationships, and their interfaces; the consequences describe trade-offs such as price and value. Patterns provide a repeatable design vocabulary for building services from reusable components.

INaaS

Contextual information delivered as service

Information as a service delivers data transformed into information relevant to a person, organization, task, or situation. Raw storage or unprocessed data is not enough. Software or analysis must add context, such as matching transport schedules to a user's location or presenting regulatory information relevant to a particular business.

BPaaS

Business process delivered as service

Business process as a service supplies a business function or workflow through cloud technologies, often combining infrastructure, platforms, applications, and information services. The process may be automated or include human steps. Examples in the book include payroll, tax planning, training, and health monitoring.

Cloud of things and services (CoTS)

Cloud managing connected devices

A Cloud of things and services is a specialized cloud environment that processes information from connected devices and coordinates the services that support them. For example, a system could monitor streetlights, identify which require maintenance, and organize the response. The concept links connected physical objects with automated cloud-based workflows.

Cloud bursting

Using another cloud for extra capacity

Cloud bursting occurs when a cloud service uses resources from another cloud to meet a rise in demand or support continuity. It relies on the ability to connect the services and preserve the required performance and agreements. It is one way to gain capacity without permanently maintaining that capacity in the primary environment.

Parkerian hexad

Six-part information security model

The Parkerian hexad describes information security through confidentiality, possession or control, integrity, authenticity, availability, and utility. It expands the familiar three-part CIA model by distinguishing control of information, confidence in its origin, and whether it remains useful to authorized users. The book uses these dimensions to help express security requirements.

Cloud service exchange

Marketplace for cloud services

A cloud service exchange is the author's proposed marketplace for discovering, pricing, and trading cloud services in real time. Providers and consumers would match services according to need and price, with interoperability allowing one service to be replaced by another. The proposal is more straightforward for infrastructure and platform services than for complex business processes.

Cloud maturity model

Scale for cloud adoption capability

The cloud maturity model assesses how well an organization purchases, uses, and manages cloud services. Its levels are performed, defined, managed, adapted, and optimized. It considers people, processes, monitoring and reporting, governance, and financial management. Organizations can use it to identify weaknesses and plan improvements rather than treating adoption as a one-time move.

Elasticity

Scaling capacity with demand

Elasticity is the ability to scale pooled cloud resources out when demand increases and back in when demand falls. The book distinguishes this horizontal scaling from vertical scaling, which increases the capacity of an individual resource. Elasticity can limit idle capacity, but it depends on suitable applications, networks, service agreements, and transparent measurement.

About the Author

Nayan B. Ruparelia is an experienced technology professional and entrepreneur based in London. With over three decades of experience in the tech industry, he has established himself as a notable figure in cloud computing and information technology. Ruparelia's career highlights include serving as the Chief Technologist at Hewlett Packard UK from 2007 to 2015, where he likely gained extensive knowledge of enterprise-level technology solutions. His background in both entrepreneurship and corporate technology leadership positions him as a knowledgeable author on the subject of cloud computing, bridging the gap between technical concepts and business applications.

Download PDF

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

Download EPUB

To read this Cloud Computing 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.42 MB     Pages: 19
Want to read the full book?
Follow
Listen7 mins
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...