Book Review: Architecting the Cloud
benrothke writes Most books about cloud computing are either extremely high-level quasi-marketing tomes about the myriad benefits of the cloud without any understanding of how to practically implement the technology under discussion. The other type of cloud books are highly technical references guides, that provide technical details, but for a limited audience. In Architecting the Cloud: Design Decisions for Cloud Computing Service Models, author Michael Kavis has written perhaps the most honest book about the cloud. Make no doubt about it; Kavis is a huge fan of the cloud. But more importantly, he knows what the limits of the cloud are, and how cloud computing is not a panacea. That type of candor makes this book an invaluable guide to anyone looking to understand how to effective deploy cloud technologies. Keep reading below for the rest of Ben's review.
Architecting the Cloud: Design Decisions for Cloud Computing Service Models (SaaS, PaaS, and IaaS)
author
Michael Kavis
pages
224
publisher
Wiley
rating
9/10
reviewer
Ben Rothke
ISBN
978-1118617618
summary
Extremely honest and enlightening book on how to effectively use the cloud
The book is an excellent balance of the almost boundless potential of cloud computing, mixed with a high amount of caution that the potential of the cloud can only be manifest with effective requirements and formal security architecture.
The full title of the book is: Architecting the Cloud: Design Decisions for Cloud Computing Service Models: SaaS, PaaS, and IaaS. One of the mistakes of using the cloud is that far too many decision makers rush in, without understanding the significant differences (and they are significant) between the 3 main cloud service models.
In chapter 1, he provides a number of enthusiastic cloud success stories to set the stage. He shows how a firm was able to build a solution entirely on the public cloud with a limited budget. He also showcases Netflix, whose infrastructure is built on Amazon Web Services (AWS).
Chapter 3 is titled cloud computing worst practices and the book would be worth purchasing for this chapter alone. The author has a number of cloud horror stories and shows the reader how they can avoid failure when moving to the cloud. While many cloud success stories showcase applications developed specifically for the cloud, the chapter details the significant challenges of migrating existing and legacy applications to the cloud. Such migrations are not easy endeavors, which he makes very clear.
In the chapter, Kavis details one of the biggest misguided perceptions of cloud computing, in that it will greatly reduce the cost of doing business. That is true for some cloud initiatives, but definitely not all, as some cloud marketing people may have you believe.
Perhaps the most important message of the chapter is that not every problem is one that needs to be solved by cloud computing. He cites a few examples where not going with a cloud solution was actually cheaper in the long run.
The book does a very good job of delineating the differences between the various types of cloud architectures and service models. He notes that one reason for leveraging IaaS over PaaS, is that when a PaaS provider has an outage, the customer can only wait for the provider to fix the issue and get the services back online. With IaaS, the customer can architect for failure and build redundant services across multiple physical or virtual data centers.
For many CIO's, the security fears of the cloud means that they will immediately write-off any consideration of cloud computing. In chapter 9, the author notes that almost any security regulation or standard can be met in the cloud. As none of the regulations and standard dictate where the data must specifically reside.
The book notes that for security to work in the cloud, firm's needs to apply 3 key strategies for managing security in cloud-based applications, namely centralization, standardization and automation.
In chapter 10, the book deals with creating a centralized logging strategy. Given that logging is a critical component of any cloud-based application; logging is one of the areas that many firms don't adequate address in their move to the cloud. The book provides a number of approaches to use to create an effective logging strategy.
The only issue I have with the book is that while the author is a big fan of Representational state transfer (REST), many firms have struggled to obtain the benefits he describes. RESTful is an abstraction of the architecture of the web; namely an architectural style consisting of a coordinated set of architectural constraints applied to components, connectors and data elements, within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements.
I think the author places too much reliance on RESTful web services and doesn't detail the challenges in making it work properly.RESTful is not always the right choice even though it is all the rage in some cloud design circle.
While the book is part of the Wiley CIO Series, cloud architects, software and security engineers, technical managers and anyone with an interest in the cloud will find this an extremely valuable resource.
Ironically, for those that are looking for ammunition why the cloud is a terrible idea, they will find plenty of evidence for it in the book. But the reasons are predominantly that those that have failed in the cloud, didn't know why they were there in the first place, or were clueless on how to use the cloud.
For those that want to do the cloud right, the book provides a vendor neutral approach and gives the reader an extremely strong foundation on which to build their cloud architecture.
The book lists the key challenges that you will face in the migration to the cloud, and details how most of those challenges can be overcome. The author is sincere when he notes areas where the cloud won't work.
For those that want an effective roadmap to get to the cloud, and one that provides essential information on the topic, Architecting the Cloud: Design Decisions for Cloud Computing Service Models is a book that will certainly meet their needs.
Reviewed by Ben Rothke.
You can purchase Architecting the Cloud: Design Decisions for Cloud Computing Service Models (SaaS, PaaS, and IaaS) from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page. If you'd like to see what books we have available from our review library please let us know.
The full title of the book is: Architecting the Cloud: Design Decisions for Cloud Computing Service Models: SaaS, PaaS, and IaaS. One of the mistakes of using the cloud is that far too many decision makers rush in, without understanding the significant differences (and they are significant) between the 3 main cloud service models.
In chapter 1, he provides a number of enthusiastic cloud success stories to set the stage. He shows how a firm was able to build a solution entirely on the public cloud with a limited budget. He also showcases Netflix, whose infrastructure is built on Amazon Web Services (AWS).
Chapter 3 is titled cloud computing worst practices and the book would be worth purchasing for this chapter alone. The author has a number of cloud horror stories and shows the reader how they can avoid failure when moving to the cloud. While many cloud success stories showcase applications developed specifically for the cloud, the chapter details the significant challenges of migrating existing and legacy applications to the cloud. Such migrations are not easy endeavors, which he makes very clear.
In the chapter, Kavis details one of the biggest misguided perceptions of cloud computing, in that it will greatly reduce the cost of doing business. That is true for some cloud initiatives, but definitely not all, as some cloud marketing people may have you believe.
Perhaps the most important message of the chapter is that not every problem is one that needs to be solved by cloud computing. He cites a few examples where not going with a cloud solution was actually cheaper in the long run.
The book does a very good job of delineating the differences between the various types of cloud architectures and service models. He notes that one reason for leveraging IaaS over PaaS, is that when a PaaS provider has an outage, the customer can only wait for the provider to fix the issue and get the services back online. With IaaS, the customer can architect for failure and build redundant services across multiple physical or virtual data centers.
For many CIO's, the security fears of the cloud means that they will immediately write-off any consideration of cloud computing. In chapter 9, the author notes that almost any security regulation or standard can be met in the cloud. As none of the regulations and standard dictate where the data must specifically reside.
The book notes that for security to work in the cloud, firm's needs to apply 3 key strategies for managing security in cloud-based applications, namely centralization, standardization and automation.
In chapter 10, the book deals with creating a centralized logging strategy. Given that logging is a critical component of any cloud-based application; logging is one of the areas that many firms don't adequate address in their move to the cloud. The book provides a number of approaches to use to create an effective logging strategy.
The only issue I have with the book is that while the author is a big fan of Representational state transfer (REST), many firms have struggled to obtain the benefits he describes. RESTful is an abstraction of the architecture of the web; namely an architectural style consisting of a coordinated set of architectural constraints applied to components, connectors and data elements, within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements.
I think the author places too much reliance on RESTful web services and doesn't detail the challenges in making it work properly.RESTful is not always the right choice even though it is all the rage in some cloud design circle.
While the book is part of the Wiley CIO Series, cloud architects, software and security engineers, technical managers and anyone with an interest in the cloud will find this an extremely valuable resource.
Ironically, for those that are looking for ammunition why the cloud is a terrible idea, they will find plenty of evidence for it in the book. But the reasons are predominantly that those that have failed in the cloud, didn't know why they were there in the first place, or were clueless on how to use the cloud.
For those that want to do the cloud right, the book provides a vendor neutral approach and gives the reader an extremely strong foundation on which to build their cloud architecture.
The book lists the key challenges that you will face in the migration to the cloud, and details how most of those challenges can be overcome. The author is sincere when he notes areas where the cloud won't work.
For those that want an effective roadmap to get to the cloud, and one that provides essential information on the topic, Architecting the Cloud: Design Decisions for Cloud Computing Service Models is a book that will certainly meet their needs.
Reviewed by Ben Rothke.
You can purchase Architecting the Cloud: Design Decisions for Cloud Computing Service Models (SaaS, PaaS, and IaaS) from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page. If you'd like to see what books we have available from our review library please let us know.
I live on an apartment An the ninety-ninth floor of my block And I sit at home lookin' out the window Imaginin' the world has stopped
What would Bennett Haselton do?
the "Cloud to Butt" add-on.
How would a cloud provider assure customers that their data will remain secure if they go bankrupt or just quit the business?
As of now, if a provider tanks, the servers go to the auction house, and in theory, are blanked. However, in reality, there is no assurance of that, and the buyer will get all data stored free and clear. If they wanted to do a multi-terabyte torrent of a failed bank's account and transaction data, they can, and nothing legally could stop them.
Then you have yet to unlock the full hilarity potential of the internet...
https://chrome.google.com/webs...
Looks like a good read! I am curious if there is any information pertaining to the acceptable use of the cloud in unique IT environments such as healthcare.
Somewhere, something incredible is waiting to be known. -Carl Sagan
"Architecting?" Is that really a word? Suposebly so... Irregardless, this looks like a good read.
Most providers of "cloud" services are *not* free. You pay for time, workload, network, storage, etc.
In IaaS (infrastructure as a service) you're basically just renting time/space/bandwidth on someone else's equipment.
I have an information for you, that while some spend time architecting, others designerize. You'll have to acclimatizate yourself to how folks vocalizate now. Here, drink a water. (Sigh)
The reviewer does not indicate if the book is written in English, which is relevant because the title clearly is not.
So maybe Jennifer Lawrence should write a book, because she "knows what the limits of the cloud are" too!
Until such time that the tech community of the world can and will effectively deal with (i.e. either convince to stop misbehaving or just kill 'em) all the brilliant psychopathic programmers in their mist that create malware and viruses that defraud millions of people, then it is plain madness and criminal negligence to encourage people to entrust their data to some unknown and unmonitored external entity such as the 'cloud'.
Until that time, safe and productive cloud computing is just a fantasy. It's a solution in search of problem. Avoid it.
The main bottleneck of "the cloud" is standards. Unless organizations can easily swap vendors and make their own (optional) backups without hassles, the "cloud" will continue to be a fractured, risky, and messy place.
The problem is that there are no incentives to standardize because service companies don't want the market to become a commodity because commoditization usually eats their profits (at least in the industrialized world) just like it did with PC's. They want you to be locked in to Their Way so that you can't leave for competitors.
I don't know how to solve that problem. Telling big players to sacrifice profits will go over like a lead balloon.
Standards would include configuration portals, directory structures, and "stack version sets" that combine application-language + database + web-server versions etc. into a single stack version number for cross-comparison shopping. Shopping based on differing versions of each component is not realistic because it's not realistic for a cloud-provider to test and support kajillion version combo's.
Either that, "the cloud" could support virtual servers such that one can take their virtual server elsewhere when needed, but then "the cloud" is mostly just offering equipment hosting rather than "cloud services", which gets away from the initial concept. It's a chip cloud.
Table-ized A.I.
here https://kickass.to/architecting-the-cloud-design-decisions-for-cloud-computing-service-models-pdf-t8931864.html
I maintain several cloud based applications. STAY AWAY.
There is no time when "The Cloud" is a good idea. In fact, I'd say it's even worse than "Closed source" software. Because no you not only lose access to the application, you lose access to your data as well. And trust me, the cloud service provider will use that access against you. I have yet to see a contract negotiation with a cloud service provider that didn't eventually devolve into the Cloud threatening to cut off access to the data with no option to export if the user didn't agree to unfavorable terms. This doesn't happen "Sometimes" this happens every time... with multiple vendors. They are very friendly and the rates are cheap at first, but after you've been with them for a few years... Then they start turning the screws. Unless you control "The cloud" yourself, stay very very far away.
The SANS Internet Storm Center was built just for that - https://isc.sans.edu/
Will an experienced admin (20+ years *NIX) that's currently using RackSpace (dedicated and cloud) learn anything from this book? It's so hard to tell from this review.
I've been using RackSpace for a few months now and I find that it's not much different than hosting the servers myself except I don't have to deal with things like router/switch configuration and hardware replacements.
"Most books about cloud computing are either extremely high-level quasi-marketing tomes about the myriad benefits of the cloud without any understanding of how to practically implement the technology under discussion. "
Or....?
You didn't even get your first sentence right, I'm not going to read about the rest of your thoughts.
Listen, I'm a network engineer with over 30 years of experience.
The "cloud" is not a new idea. It's a new buzzword for a very OLD idea. It simply means storing your data on somebody else's servers all under their control.
Its fine for individuals that travel all over the world and don't have access to servers, but if your in a large corporation or a government agency, then you already have servers, already have internet access, and so you have everything you need to establish your own "cloud" at no additional expense. WHY would you pay some 3rd party to host your data, where they can get to it and do who knows what with it?
Second, it is a buzzword that is used to get gullible suits to think that they can get rid of their IT depatments.
It's not like all this hasn't been proven already.
The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
The Cloud Song by Cynthia Sherwood
(Sing to the tune of “The Farmer in the Dell”)
The puffy, flat, white clouds
We call them cumulus
Hi-ho-a-cloud-e-oh
The puffy, flat, white clouds.
The feathery, thin white clouds
Are cirrus
high in the sky
Hi-ho-a-cloud-e-oh
The feathery, thin white clouds.
The gray and foggy clouds
Are stratus
low in the sky
Hi-ho-a-cloud-e-oh
The gray and foggy clouds.
The dark and stormy clouds
Watch out for nimbus
rain
Hi-ho-a-cloud-e-oh
The dark and stormy clouds.
Get this at Super Teacher Worksheets - www.superteacherworksheets.com
Why don't we just call "the cloud" by the name we used for it decades ago?
"Mainframe", that is.
If Pandora's box is destined to be opened, *I* want to be the one to open it.
Is there a fully described real world example, we all could take a look at before committing ourselves to the 'Cloud'?
Correct link
All cloud naysayers are by their very definition insane.
Ever hear of Amazon? 100% cloud. Over $50B in revenue.
What about salesforce.com100% cloud. Over $20B in revenue.
If you don’t believe in the cloudyou are a delusional person.
who cares about the grammar....like u word for the university library?
if u r tech...grammar is a has been.
this is a take off of lucy in the cloud skie with diamonds!
but the beathles didn't have a saas model to write songs...so they just were best!
Pete best!
95% of these comments here are from people who know ZERO about the cloud.
just loudmouths and jokes who want to yelp.