Book Review: Getting Started with Oracle Public Cloud

Book Review:  Getting Started with Oracle Public Cloud by Hemant Kumar Mehta: Publisher- Packt: ISBN- 13: 978-1-78217-810-1

 

Getting Started with Oracle Public Cloud is high level summary of services offered by Oracle public cloud. This book also covers essential requirements to how to start working with Oracle Public Cloud. This book can be used as first step to understand Oracle public cloud.

Book has been divided in chapters very neatly as per the services offered by Oracle Public Cloud. Book also layout few of the best practices of Oracle Public Cloud for its various services.

The book part\, which I like most is chapter 2, which talks about transitioning from on premises to cloud.

 
As name suggest book provides very initial understanding of Oracle Cloud but nevertheless the book is good starting point.

Good book to lay foundation for developer as well as management to start understand Oracle Public Cloud.

One could get more info aabout book at http://bit.ly/IjUmUa.

Disclaimer: I did not get paid to review this book, and I do not stand to gain anything if you buy the book. I have no relationship with the publisher or the author. I got electronic format of book from publisher for review.

Cloud Criticism

While whole of IT industry is behind Cloud Computing. But are we paying enough attention to dangers of Cloud Computing! Most probably not. I have tried to list few of the points:

1. Lock in of data in proprietary format.
2. Lock in of business processes in third party systems.
3. Lost control over business data and its presentation (Recent spat between Wikileaks and Tableau).
4. Always on network which is in contradiction of “Eight fallacies of distributed computing”.
5. Very few cloud vendors.

Reference:

1. http://www.dbta.com/Articles/Editorial/Think-About-It/Environmental-Group-Targets-Cloud-Computing-Criticism-Justified3f--66406.aspx
2. http://minutiaeetal.wordpress.com/2008/10/25/three-critiques-of-cloud-computing/
3. http://www.riorevuelto.org/site/index.php?text=view&id_articulo=5418
4. http://www.informationweek.com/cloud-computing/blog/archives/2008/10/cloud_computing_4.html
5. http://www.museumstuff.com/learn/topics/cloud_computing::sub::Criticism_Of_The_Term
6. http://gcn.com/Articles/2009/09/14/Reality-Check-cloud-computing-as-red-herring.aspx
7. http://www.cio.com/article/498795/A_Great_Cloud_Debate_Zittrain_Counters_CIO.com_Criticism_
8. http://www.zdnet.com/blog/service-oriented/cloud-computings-earthly-bonds/1114
9. http://www.webpronews.com/topnews/2008/09/29/open-source-guru-rails-against-cloud-computing-%E2%80%98hype%E2%80%99
10. http://www.infoworld.com/d/cloud-computing/busted-three-myths-cloud-computing-098?page=0,0

What questions (non financial) should I ask to a Cloud provide?

1. Number of years in service?
2. Number of subscribers?
3. Number of users?
4. Min number of users per subscriber?
5. Max number of users per subscriber?
6. Average number of users per subscriber?
7. Geographic spread of subscribers?
8. Mode by which Cloud can be accessed ( Browser, hand held device – mobile phone – which one, etc)
9. Does app has offline client?
10. Browser compatibility
11. List of business processes affected
12. Severity of affect to each business process (just touch, requires change, need complete change)
13. How to integrate with existing business systems – batch/real, synchronous/asynchronous, technology/platform?
14. Do employees need training?
15. Does Cloud affect master data?
16. How to integrate with Single Sign On (SSO)?
17. Does proposed cloud will capture any sensitive information (trade secret, patent, customer data, etc)?
18. What are the bandwidth requirements of proposed Cloud?
19. Does proposed Cloud have SSL support?
20. Does Cloud provider share with you external penetration tests and internal network security audits periodically?
21. Does provider have a documented policy for "hardening" the OS under Web and other servers?
22. Does provider have a documented set of controls to separate data and security information among customer applications?
23. Does provider perform background checks on personnel with administrative access to servers and applications?
24. Does provider has documented process for security alerts from IT partners?
25. What are the procedures for business continuity and disaster recovery?
26. Does provider certify the security of scripts and integration code; documented procedures for installing security patches
27. Does provider offer application- or transaction-based intrusion- detection services?
28. Does provider has documented identity management and help desk procedures?
29. What percentage of security staff has security industry certification?
30. What is the average experience of provider's security staff in information and network security?
31. What is the provider’s operational model: a. Self Hosting b. Co-location c. Managed Hosting d. Cloud Computing?
32. Is the provider's data center N + 1 for power?
33. Provider's Data facility: 1. Tier III 2. Tier IV
34. Is the provider's data center certified SAS 70 Type II or Type 1?
35. How many data centers does the provider have?
36. Which data centers will be used to server the application?
37. Is there a DR plan if a data center becomes unavailable?
38. Does the provider use at least 3 ISPs? Who are they?
39. Can a private connection to my enterprise WAN be provided?
40. Does the provider have network redundancy? How is this achieved?
41. How is network latency mitigated?
42. Can the provider provide location specific SLA's measured by a third party benchmarking service?
43. What are the hardware and software components provided by the provider?
44. Are provider servers dedicated or shared? If shared, by what method?
45. Is infrastructure redundant? If so, how is this accomplished?
46. What is Backup and retention schedule?
47. What monitoring is done as well as the interval, and reports that are available to review?
48. Is there staff 24/7? If not, what hours is staff available?
49. What is the provider's change management, patch management and upgrade policies and procedures?
50. What are the downtime notification policies (i.e. is advance notification given? How much?)?
51. Will a staging server/staging sand box be available for testing prior to production deployment?
52. Does provider has sand box for development?
53. How is security alerts handled? What are the security policies?
54. Do you have clear Service Level Agreements (SLAs) established with the service provider?
55. What kind of System Monitoring provided by the service provider?
56. What kind of help-desk support is available?
57. What are the change management processes available from the service provider?
58. Does the service provider provide you a staging environment to test changes before they are promoted to production?
59. Will the service provider support for full data and rule customization recovery on contract termination?
60. What API’s are exposed by service provider to develop application over cloud?
61. What API’s are exposed by service provider to deploy application over cloud?
62. Does my enterprise need new licensees of app servers/database or any other applications to be deployed over cloud?
63. How much time is needed to set up a proof of concept or trial demo?
64. How can offering being customized?
65. Industry references
66. Historical records of service availability?

What need to be standardized in Cloud Computing?

1. Federated Identity across cloud and non cloud applications
2. Meta data hierarchy and its exchange mechanism across cloud
3. Data exchange – real time and import/export standards
4. Standards for SLA – machine readable
5. Orchestration and Chorographic standards across cloud to create composite applications
6. Policy and Governance standards
7. Monitoring, billing, auditing, logging, and notification standards
8. Common Data Model across clouds for interfacing cloud resources
9. Privacy standards
10. Global standards (across government bodies and across governments) for data movement and its residency
11. Description of Non Functional requirements (Availability, Scalability, Latency, etc)

Cloud Promises and Truth

1.
Promise: Scalability
Truth: Absolutely (Think of Salesforce, EC2, Azure, AppEngine, etc)
2.
Promise: Peak Load Capacity on the fly
Truth: Think of Wimbledon, famous case study of Washington and EC2
3.
Promise: Zero Capex
Truth: Reduced not Zero (Think of appliance needed, integration required, and one time fee)
4.
Promise: Lower Beta and Testing cost
Truth: Yet to prove it
5.
Promise: Geographic Independence
Truth: Depends upon cloud provider. But remember of compliance challenges
6.
Promise: Device and Operating System and Technology platform independence
Truth: Depends upon genre of Cloud ( SaaS, PaaS or IaaS). Consider licensing issues.
7.
Promise: Multi tenancy enhances the utilization
Truth: Theoretically, Yes but Still to prove
8.
Promise: Centralization reduces cost
Truth: Theoretically, Yes but Still to prove
9.
Promise: Consistent Performance
Truth: Mostly. Consider network latency, bandwidth, 8 fallacies of distributed computing (http://blogs.sun.com/jag/resource/Fallacies.html)
10.
Promise: Enhanced Reliability
Truth: Questionable (jus remember EC2, AppEngine, and Salesforce outage)
11.
Promise: Cloud Computing Removes the Need for an Internal IT Department
Truth: Lie
12.
Promise: Applications Can Be Moved without Change to the Cloud
Truth: Not possible as of today
13.
Promise: It Is Easy to Switch Cloud Computing Vendors
Truth: Not possible as of today
14.
Promise: Moving to Cloud Computing Just Requires a Credit Card—It’s Computing as a Utility
Truth: Lie. Think of integration, training and other stuff

Consideration while choosing a Cloud Service Provider (Infrastructure as a Service – Cloud based Virtual Data Centre)

Any organization while purchasing Cloud services especially, Infrastructure as a Service which is essentially Cloud based Virtual Data Centre should give due consideration to following points:
1. Ability to port and run existing Enterprise Applications ( possibly unchanged) in the cloud
2. Self service portal for functional users (not of applications but of cloud).
3. Configurability, visibility and control over virtual data centre
4. Import and Export of virtual images
5. Support for existing software licenses
6. Accommodation of appliances
7. Role based user access control
8. Policy Management, Cost control and charge back
9. Team collaboration and Workflow
10. SLAs
11. Compliance
12. Access to log and audit data
13. Physical security of data centre
14. Disaster recovery plan
15. Security of data and Intellectual Property (IP)
16. Support and Training
17. Documentation
18. References

Book Review: Cloud Computing – Implementation, Management and Security

Book Review: Cloud Computing – Implementation, Management and Security by John W. Rittinghouse and James F. Ransome: Publisher- CRC Press: ISBN- 13: 978-1-4398-0680-7

This is one book on cloud computing. From the topic it seems that book is targeted at the cloud provider community but it looses focus very often. Nevertheless it tries to provide other side of story which no other book in market is providing.

Book consists of nine chapters which covers history of computers, various services offered by cloud, introduction to virtualization, standards in cloud, some talk about security and privacy in cloud, and accessing the cloud. Book also have two appendices which covers hands on Sun VirtualBox and case study on executive talk on cloud adoption.

Book provide lot of references which I like particularly. Book also scratches few of the topic which no other book has covered ( at least I have not encountered) like security and privacy in cloud in detail ( there is scope of much improvement), identity management in cloud ( again with huge scope of improvement) etc.

I suggest, read this book once but certainly it does not deserve to be in my bookshelf.

Disclaimer: I did not get paid to review this book, and I do not stand to gain anything if you buy the book. I have no relationship with the publisher or the author.

One can get more information about book and related topics from:

1. Amazon: http://www.amazon.com/Cloud-Computing-Implementation-Management-Security/dp/1439806802
2. Flipkart: http://www.flipkart.com/cloud-computing-john-rittinghouse-james-book-1439806802
3. Dr. John W. Rittinghouse resume: http://www.aphanes.net/JR%20Bio.html

Revelation about IaaS

While discussing cloud with my colleagues, one revelation comes to me. Infrastructure as Service dimension of cloud is just better access of Data Center. A Data Center which offers its administrative activities as API and supports virtualization.

Levels of Multitenancy

Before diving into multitenancy, let us understand how a typical application is structured.

From the picture supplied it is very clear that a contemporary application is based on layered architecture and runs on infrastructure and network on which typical servers sustained.

If you look into maturity levels of SaaS applications it seems that multitenancy exists only at Database level where one data stores multiple tenants a.k.a. Salesforce.com. This picture depicts a picture that before SaaS there was no concept of multitenancy.

If you dig little bit, it is clear that multitenancy can occur at any level. At Network and Infrastructure level collocation is prime example of multitenancy. View level multitenancy is at its best at blog sites. Business layer level multitenancy is very much present in Applications in Cloud.

Cloud Computing Risks

1. Risks when consuming Cloud
a. Availability
b. Data back up
c. Disaster recovery
d. Problem Resolution
e. Quality of Service
f. Security
g. Total Cost of Ownership (TCO)
h. Compliance
2. Risks when Supporting the cloud
a. Fail over and redundancy
b. Provisioning
c. Security
d. Adherence to SLAs
e. Metering
f. Disaster recovery

Cloud Computing and Green IT

If you list latest buzz word in IT, certainly Green IT and Cloud will top this list. But does any body care about Green IT and SOA. I say no one. As a business person, I care only about my CapEx and OpEx. If on the way, I get some Browne Points for saving Earth, excellent.

So how to get Brownie Points and maximize the profit.

Cloud computing focuses on reduction of CapEX and converting the same into OpEx and Green IT focuses on CapEX as well as OpEx reduction.

Green IT focuses on reduction in Electricity Bills and using Bio Friendly materials and ways to reduce cost. Cloud computing give emphasis to sharing of resources to reduce CapEX. From this point of view Green IT and Cloud are tightly coupled.

Role of clouds in SOA

Cloud is a cost-effective deployment platform for your SOA

Basic level: Use virtualized platform as a convenient provisioning tool
Advanced level: Service and application Architects, designers and developers architect, design and develop services which auto-scale, are multi-tenant and possibly use parallel computing

Book Review: Cloud Computing and SOA Convergence in Your Enterprise A Step-by-Step Guide

Book Review: Cloud Computing and SOA Convergence in Your Enterprise A Step-by-Step Guide by David S. Linthicum: Publisher- Addison Wesley: ISBN- 13: 978-0-13-600922-1

In this book David does a fantastic job of showing that SOA and Cloud are two faces of same coin. Cloud Computing is natural extension of SOA. Book is written keeping business executives in consideration. For technical folks this may seems to be boring and very shallow but for Business Executives this book has covered lot of ground. David has developed a fine business case for Cloud computing through out the book and explains different services of cloud computing in very seamless fashion.

David has introduces a model for various services Cloud offers in start of book and then majority of book is devoted to elaboration of that model. This model seems to be very comprehensive and agonistic to various offerings in the market. The biggest drawback I see in this book is that there is no or very little reference to existing cloud offerings in the market. Nevertheless, book is good read and introduces cloud computing to business folks in very easy manner.

I hope in future there will be some similar books which will cloud computing from technical perspective.

Disclaimer: I did not get paid to review this book, and I do not stand to gain anything if you buy the book. I have no relationship with the publisher or the author.

Further reading: Following are the book covering cloud computing:
1. Cloud Application Architectures: Building Applications and Infrastructure in the Cloud by George Reese (http://www.amazon.com/Cloud-Application-Architectures-Applications-Infrastructure/dp/0596156367)
2. Cloud Security and Privacy: An Enterprise Perspective on Risks and Compliance by Tim Mather (http://www.amazon.com/Cloud-Security-Privacy-Enterprise-Perspective/dp/0596802765)
3. Cloud Computing, A Practical Approach by Anthony T. Velte, Toby J. Velte and Robert Elsenpeter (http://www.amazon.com/Cloud-Computing-Practical-Approach-Velte/dp/0071626948)
4. Dot Cloud: The 21st Century Business Platform Built on Cloud Computing by Peter Fingar (http://www.amazon.com/Dot-Cloud-Business-Platform-Computing/dp/0929652495)
5. Cloud Computing: Implementation, Management, and Security by John W. Rittinghouse (http://www.amazon.com/Cloud-Computing-Implementation-Management-Security/dp/1439806802)


One can get more information about book and related topics from:

1. Amazon: http://www.amazon.com/Cloud-Computing-Convergence-Enterprise-Step/dp/0136009220
2. Flipkart: http://www.flipkart.com/b2b-application-integration-david-linthicum/0201709368-jqw3fi8wab
3. David S. Linthicum: http://www.davidlinthicum.com/

The Hidden Cost of Cloud Computing

One of the most obvious benefits of Cloud Computing is conversion of CaEx to OpEx which brings in cost reduction. But one must remember there are no free lunches. Cloud Computing has its own set of hidden costs which must be considered while deciding about.

1. What are the viable paths to move or replace legacy application into cloud?
2. What are the changes required to integrate cloud or non cloud applications?
3. What technological and business processes will change to take benefits of Cloud?
4. What are the trade offs of using Private/Public/Hybrid clouds for each application?
5. What are the skills to be acquired and/or upgraded to take benefit of Cloud?

I have just listed Whats but to get insight do 5 Wives and 2 Husbands Analysis.

Architectural Consideration for application to be deployed over Cloud

Cloud computing is new way of deploying a application. This deployment topology brings in its own pleasant moments and surprises. For an architect and designer Cloud opens up new avenue and dent into capacity planning. Now a programmer of application to be deployed on a cloud can spread over logical hardware at run time without involvement of any hardware and network person’s involvement.

While architecting a application for Cloud few aspects to be taken into consideration.

1. Scale: Application to be deployed on Cloud can grow and shrink dynamically based on load and can be controlled programmatically.
2. Coupling: Application to be developed in highly loosely coupled. Here SOA principles can come handy.
3. Clustering and Virtualization: Clustering and Virtualization is inherent to cloud architecture. These two aspects must be considered in detail while architecting an application.
4. Failure: Clod application must be architected to fail in parts, autonomic and fault tolerant fashion to get full benefits of Cloud architecture.

These are the considerations specific to Cloud. There could be several other which we can learn with experience over Cloud.

Cloud Computing Demystified

What is cloud computing? No one knows. Every one has his own definition to suite his needs. To add to confusion I also add my two cents to definition of cloud.

In my point of view cloud computing is an umbrella term for XaaS and virtualized IT assets supported by Utility, Grid and Autonomic Computing in one offering. But due to early in life cycle of evolution not all cloud offering are based on Utility, Grid and Autonomic computing principles. X in XaaS has many metaphors and there also exist great divide among analysts, vendors and service providers.



Infrastructure as s Service (IaaS): This is Data Centre as a Service or remotely managed data center.

Storage as a Service: This is Disk Space as a Service or in simple terms Disk Space on Demand. You can consider this as remote storage for consumer but local for application.

Database as a Service (DaaS): This service provides consumers to access and manage persistence layer (RDBMS, Hierarchal Database – LDAP, File System, etc).

Information as a Service: This is granular business services on demand. For example tax calculation for a product/service.

Software as a Service (SaaS): This is Application as a Service. Here a major portion of or full business application is offered on demand. On the extreme of Cloud is Process as a Service (process outsourcing).

Integration as a Service: It is one of the most interesting aspects of Cloud. It provide features of traditional EAI/B2B but as service.

Platform as a Service (PaaS): This is offering provide complete SDLC of Cloud hosted application/service. Most of the matured Clouds provide this service by default.

Governance as a Service: This is basically mechanism to manage cloud computing resources, typically managing topology, resource utilization, up time, policy management and other related issues.

Testing as a Service: This is facility provides sandbox testing of developed application/service using PaaS offering.

Security as a Service: Due to open nature of internet, security is must for any offering. Security as a service may offer identity management, encryption/decryption, etc.

Case Against Private Cloud

1. Change in mindset of existing IT organization
2. Lot of automation in policy enforcement
3. Addition of one more layer of complexity in IT Infrastructure
4. Additional resource – man, machine, material (Software and hardware) requirement which my not be justified in light of RoI and TCO
5. Disruption in existing IT infrastructure
6. Shifting from private cloud to public cloud may become challenging once benefits of cloud computing are understood and internalized by IT and business.