What do you think?
Rate this book
Cloud Computing, revised and updated edition
An updated, revised, and comprehensive overview of the concepts related to cloud computing, including recent applications, innovations, and its future evolution.
In this Essential Knowledge volume, Nayan B. Ruparelia provides an updated and revised version of Cloud Computing , first published in 2016, to address not only the fact that cloud computing has become a ubiquitous part of mainstream computing since then but also has made strides in other key aspects of the technology’s development,
An indispensable guide to cloud computing for the layperson, Cloud Computing cuts through the technical jargon and details that are irrelevant to nontechnologists, as well as the marketing hype, and explains clearly what cloud computing is, when to use it (and when not to), how to select a cloud service, how to integrate it with other technologies, and what the best practices are for its adoption.
In this Essential Knowledge volume, Nayan B. Ruparelia provides an updated and revised version of Cloud Computing , first published in 2016, to address not only the fact that cloud computing has become a ubiquitous part of mainstream computing since then but also has made strides in other key aspects of the technology’s development,
An indispensable guide to cloud computing for the layperson, Cloud Computing cuts through the technical jargon and details that are irrelevant to nontechnologists, as well as the marketing hype, and explains clearly what cloud computing is, when to use it (and when not to), how to select a cloud service, how to integrate it with other technologies, and what the best practices are for its adoption.
304 pages, Paperback
Published August 1, 2023
13 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
July 9, 2024
Great introduction to cloud for non technical individuals who are looking to implement cloud.
Notes for myself:
Difference between virtualisation and cloud computing:
- Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.
- Service Visualisation helps to facilitate cloud computing features, but other features are required reporting, billing, demand management and various business processes and tools.
How to employment cloud computing in the company?
1. Consider how to standardise service offerings.
2. Make service offerings available through simple service portals
3. Track usage and cost
4. Measure their availability
5. Orchestrate demand
6. Provide security framework
7. Provide intestenious Reporting
8. Billing and charging based on usage
Cloud services:
- Integrity, promptness, quality and scope, cost analysis - contract - service level agreement (SLA)
- Operational service agreement (OSA)
- Service level objectives (SLO)- measurable of SLA- uptime, available resource capacity, response time, delivery time
Cloud models:
- Infrastructure as a service (IaaS) eg store pictures data in a cloud use the cloud infrastructure , file transfer
- Platform as a service (PaaS) eg IT provides a platform complete with hardware, operation systems and specified softwares.
- software as a service (SaaS) eg
IT enterprise architecture domains/stacks:
- Technology: IT infrastructure, middleware and operating systems -platform as a service and infrastructure as a service
- Application architecture: software application and their interactions with business processes - saas
- Data architecture: data assets and management - information as a service
- Business Architecture: translate business strategy into IT strategy, relevant governance framework and definition of business processes. - business as a service
Deployment model:
- public cloud - disadvantage of integrity and security
- private cloud- provide service to one entity
- Community cloud- middle ground between public and private cloud.
- hybrid cloud- need computing resources from other cloud sources,
Chapter 7(5)- security and governance
-Data sovereignty refers to the idea that a country or jurisdiction has the authority and right to govern and control the data generated within its borders.
- IT security- protects confidentiality( who gets what kind of information), possession and control, integrity (unauthorised accessibility), availability (1. will the service be available from any other location? 2. how readable will it be when you want to use it? 3. will there be retain times when it won’t be available due to plan maintenance? (downtime metrics) 4. If the cloud service you hosting the data on to go down how long will it take for data to recover? 5. once recovery is complete have we lost any data? if so how many hours of data will it be?), utility ( can be used as attended by the user) of the user
- Data loss prevention refers to systems that discover, identify, monitor, manager protect data that in rest (data on hard drives) in motion (bluetooth, network- fluid transport data ), in use (spreadsheets- used day to day). Tools: Encryption- keep data secure , checksums to verify data integrity ; Monitoring -who has access?; management - to ensure stale unused data is destroyed within bound limit.
- what regulation or law the cloud service should conform to if it’s established in the country A, its users are from country B and data stored in country C when the cloud service itself is hosted in country D?
Specify the cloud service jurisdiction before buying or using it. Be aware of who will see the data? what systems will handle it? Which applications will use it? And establish legal jurisdiction of those people, infrastructure and applications
- Data Sovernity - if data consumed by multiple parties…who owns the data? who will own the data that was manipulated by intermediary? is it original/ who augmented the data or the end user? What if all of these actors were in different countries that have different data protection and ownership law? Have data ownership agreement, jurisdiction
-
Chapter 10: Information as a services-
- how current? how accurate? is it relevant? data protection laws or industry or national laws? Does it need to be backed up? For how long? Once archive end will it be delivered? What measures are taken if data compromise? What metrics apply to measure?
Chapter 15
- Incremental backup (change only the newly changed files)
- Full backup
- Backups (speed of recovery) vs archives (capability of search for data)
- Backup rotation
Notes for myself:
Difference between virtualisation and cloud computing:
- Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.
- Service Visualisation helps to facilitate cloud computing features, but other features are required reporting, billing, demand management and various business processes and tools.
How to employment cloud computing in the company?
1. Consider how to standardise service offerings.
2. Make service offerings available through simple service portals
3. Track usage and cost
4. Measure their availability
5. Orchestrate demand
6. Provide security framework
7. Provide intestenious Reporting
8. Billing and charging based on usage
Cloud services:
- Integrity, promptness, quality and scope, cost analysis - contract - service level agreement (SLA)
- Operational service agreement (OSA)
- Service level objectives (SLO)- measurable of SLA- uptime, available resource capacity, response time, delivery time
Cloud models:
- Infrastructure as a service (IaaS) eg store pictures data in a cloud use the cloud infrastructure , file transfer
- Platform as a service (PaaS) eg IT provides a platform complete with hardware, operation systems and specified softwares.
- software as a service (SaaS) eg
IT enterprise architecture domains/stacks:
- Technology: IT infrastructure, middleware and operating systems -platform as a service and infrastructure as a service
- Application architecture: software application and their interactions with business processes - saas
- Data architecture: data assets and management - information as a service
- Business Architecture: translate business strategy into IT strategy, relevant governance framework and definition of business processes. - business as a service
Deployment model:
- public cloud - disadvantage of integrity and security
- private cloud- provide service to one entity
- Community cloud- middle ground between public and private cloud.
- hybrid cloud- need computing resources from other cloud sources,
Chapter 7(5)- security and governance
-Data sovereignty refers to the idea that a country or jurisdiction has the authority and right to govern and control the data generated within its borders.
- IT security- protects confidentiality( who gets what kind of information), possession and control, integrity (unauthorised accessibility), availability (1. will the service be available from any other location? 2. how readable will it be when you want to use it? 3. will there be retain times when it won’t be available due to plan maintenance? (downtime metrics) 4. If the cloud service you hosting the data on to go down how long will it take for data to recover? 5. once recovery is complete have we lost any data? if so how many hours of data will it be?), utility ( can be used as attended by the user) of the user
- Data loss prevention refers to systems that discover, identify, monitor, manager protect data that in rest (data on hard drives) in motion (bluetooth, network- fluid transport data ), in use (spreadsheets- used day to day). Tools: Encryption- keep data secure , checksums to verify data integrity ; Monitoring -who has access?; management - to ensure stale unused data is destroyed within bound limit.
- what regulation or law the cloud service should conform to if it’s established in the country A, its users are from country B and data stored in country C when the cloud service itself is hosted in country D?
Specify the cloud service jurisdiction before buying or using it. Be aware of who will see the data? what systems will handle it? Which applications will use it? And establish legal jurisdiction of those people, infrastructure and applications
- Data Sovernity - if data consumed by multiple parties…who owns the data? who will own the data that was manipulated by intermediary? is it original/ who augmented the data or the end user? What if all of these actors were in different countries that have different data protection and ownership law? Have data ownership agreement, jurisdiction
-
Chapter 10: Information as a services-
- how current? how accurate? is it relevant? data protection laws or industry or national laws? Does it need to be backed up? For how long? Once archive end will it be delivered? What measures are taken if data compromise? What metrics apply to measure?
Chapter 15
- Incremental backup (change only the newly changed files)
- Full backup
- Backups (speed of recovery) vs archives (capability of search for data)
- Backup rotation
This entire review has been hidden because of spoilers.
August 14, 2025
I felt that this book leaned heavily on the IT side of cloud computing and much less on the computer science side. I picked it up hoping it would be more technical, but many chapters spent time on other related aspects to cloud computing such as business. I understand the author was trying to give a wide overview of all that cloud computing comprises, and I’ll admit, it’s a lot more involved than I imagined, but much of the explanations were either surface level or actually much too advanced for me to absorb.
As I said, I just wished the book had dived deeper into the science of cloud computing and the underlying code and mechanisms that make it work, or even a deeper history of how it evolved would have appealed to me more. This is personal though. I still learned quite a few new things and gained a broad understanding of the challenges and decisions companies are faced with when wanting to participate in cloud computing. A lot of the lingo has been cleared up for me, and now I know where to start if I continue my study on this topic.
As I said, I just wished the book had dived deeper into the science of cloud computing and the underlying code and mechanisms that make it work, or even a deeper history of how it evolved would have appealed to me more. This is personal though. I still learned quite a few new things and gained a broad understanding of the challenges and decisions companies are faced with when wanting to participate in cloud computing. A lot of the lingo has been cleared up for me, and now I know where to start if I continue my study on this topic.
Displaying 1 - 2 of 2 reviews