The least understood feature of cloud computing, Platform as a Service (PaaS), is also the most powerful and cost effective. This concise overview shows you why organizations that properly wield PaaS can quickly gain a strong competitive advantage. You’ll learn how PaaS enables developers to pursue low cost R&D projects, lets system administrators focus on systems rather than servers, and helps architects evaluate new technology quickly and directly.
Many reliable PaaS providers are available today, including services from Amazon, Red Hat, and Google. This book offers valuable advice for technically and not-so-technically minded people who want to understand how PaaS can change the way organizations do computing.
Get rudimentary examples of how to initiate projects with a typical PaaS provider
Consider language selection, feature set, and general capabilities when evaluating a PaaS solution
Automate tasks like continuous integration, unit tests, and builds
Learn how to design applications by understanding how PaaS works under the hood
Discover the critical difference between scaling up and scaling out
Anticipate subtle but important differences between traditional computing and PaaS computing
Change the way you think about security in the cloud
Mike McGrath is a founding member of Red Hat's OpenShift and is currently Principal Cloud Architect with over a decade of open source systems management experience. In addition to OpenShift architecture, he serves as operations manager for all of Red Hat's Platform as a Service offerings.
"Understanding PaaS" is a very short book on cloud computing specifically focusing on PaaS at a high level, the whole book is around 50 pages so you might finish the reading in one sitting. The book starts with explaining IaaS (Infrastructure as a service) which lays foundation for coming chapters. A sample VM creation with screenshots in AWS gives a real feel of having created a VM in cloud, and also adds to better understansing of concepts. The book then details into PaaS and various aspects of it. The book though does not do much justice for a beginner, as the later chapters are less focused on understanding PaaS itself in detail, but a high level strategic/architectural considerations for PaaS. I would suggest going through initial chapters in detail and then taking a call which chapters you might want to get int0 based on TOC. For shortness of the book I would go with 3.5 out of 5 starts
Bottom Line Yes, I would recommend this to a friend