Professional Documents
Culture Documents
Cloud Computing
Cloud Computing
Abstract
This white paper will help readers to know the basics of cloud computing and also to gain an understanding on how cloud computing works. I hope it will be beneficial to all people who want to save some money on infrastructures. Cloud based on demand web-services such as databases, queues, identity management, data on-demand, widgets, etc. are meeting with browser based thick-client frameworks such as AJAX, Adobe Flex, MS Silverlight, etc. to create a new breed of applications, built on a resuscitated Client/Server (Client/Server 2.0) SOA-based paradigm. The traditional "business logic" application server middle-tier is ceding the way to cloud based pay-per-use SOA. The increasing sophistication of cloud web-services platforms, the increase in browser sophistication and the availability of advanced client side IDEs will reinforce this trend. The new paradigm will simplify the development of web applications, simplify the creation of SaaS, provide better maintainability and lower TCO.
Page
2 of 21
Table of Contents
I. Cloud Computing Basics...............................................................................................................................4 II. Segment of Cloud Computing......................................................................................................................6 i. Application................................................................................................................................................6 ii. Platforms...................................................................................................................................................6 iii. Infrastructure...........................................................................................................................................7 III. Implementing Cloud Computing ...............................................................................................................8 i. Private Clouds............................................................................................................................................8 ii. Public Clouds ...........................................................................................................................................9 iii. Hybrid Clouds ......................................................................................................................................10 IV. Characteristics of Cloud computing.........................................................................................................11 i. Dynamic computing infrastructure..........................................................................................................11 ii. IT service-centric approach....................................................................................................................11 iii. Self-service based usage model.............................................................................................................12 iv. Minimally or self-managed platform.....................................................................................................12 v. Consumption-based billing.....................................................................................................................12 V. Cloud Computing Security Plan................................................................................................................14 VII. Barriers to Cloud Computing..................................................................................................................17 i. Customer Perspective..............................................................................................................................17 ii. Vendor Perspective.................................................................................................................................17 VIII. Summary ...............................................................................................................................................19 IX. Conclusion ...............................................................................................................................................20 X. Abbreviation..............................................................................................................................................21
Page
3 of 21
4 of 21
Infrastructure-as-a-Service manner.
(IaaS)
in
very
efficient
Customers can thus decide to develop their own applications, to run on their own internal private clouds, or leverage software as a SaaS application that run on public clouds. Integration and federation of services across both the public and private cloud, so-called hybrid clouds, is an emerging area of interest. The public cloud concept allows customers to develop and deploy applications with tremendous speed without the procurement and red-tape issues of dealing with potentially slow moving and costly IT departments. This also allows customers to shift traditional Capital Expenditures (CapEx) into their Operating Expenditure (OpEx) budgets. Driven by concerns over security, regulatory compliance, control over Quality of Service (QoS), vendor lock-in, and long-term costs, many larger customers, who have the economies of scale and strong IT competency, will build internal private clouds. These private clouds can provide the same cost and agility benefits as public clouds, while mitigating enterprise concerns about security, compliance, QoS, lock-in and TCO.
Page
5 of 21
i. Application
So far, the applications segment of cloud computing is the only segment that has proven successful as a business model. By running business applications over the Internet from centralized servers rather than from on-site servers, companies can cut some serious costs. Furthermore, while avoiding maintenance costs, licensing costs and the costs of the hardware required to run servers on-site, companies are able to run applications much more efficiently from a computing standpoint. On demand software services come in a few different varieties that may vary in their pricing scheme and how the software is delivered to the end users. In the past, the enduser would generally purchase a license from the software provider and then install and run the software directly from on-premise servers.
ii. Platforms
Platforms serve as an interface for users to access applications provided by partners or in some cases the customers. The following companies are some that have developed platforms that allow end users to access applications from centralized servers using the Internet. Next is the name of the platform used by the company: 1. Google (GOOG) - Apps Engine 2. Amazon.com (AMZN) - EC2 3. Microsoft (MSFT) - Windows Live
Page
6 of 21
4. Terremark Worldwide (TMRK) - The Enterprise Cloud 5. Salesforce.com (CRM) - Force.com 6. NetSuite (N) - Suiteflex 7. Mosso - Mosso, a division of Rackspace 8. Metrisoft - Metrisoft SaaS Platform
iii. Infrastructure
The final segment in cloud computing, known as infrastructure, is the backbone of the entire concept. Infrastructure vendors provide the physical storage space and processing capabilities that allow all the services described above.
Page
7 of 21
i. Private Clouds
In a private cloud, the infrastructure for implementing the cloud is controlled completely by the enterprise. Typically, private clouds are implemented in the data center of the enterprise and managed by internal resources. A private cloud maintains all corporate data in resources under the control of the legal and contractual umbrella of the organization. This eliminates the regulatory, legal and security concerns associated with information being processed on third party computing resources. The private cloud can also be used by existing IT departments to dramatically reduce their costs and as an opportunity to shift from a cost center to a value center in the eyes of the business. As an example, the following diagram depicts the key architectural elements of a private cloud utilizing Oracle scalabilities:
Page
8 of 21
9 of 21
difficult to document the physical location of data at any particular moment. These issues result in potential regulatory compliance issues that include the use of public clouds for certain organizations or business applications. Not all public cloud based applications can provide the necessary flexibility and functionality needed by business users. For this reason, customers require the ability to take preferred functionality from one cloud application and combine it with another, creating a cloud based component application. This is still an emerging area of development with some early companies, such as Cast Iron, providing integration of a wide range of cloud-based applications. Ultimately, many customers may decide that the private cloud offers more flexibility and develop new applications themselves.
Page
10 of 21
Page
11 of 21
v. Consumption-based billing
Finally, cloud computing is usage-driven. Consumers pay for only what resources they use and therefore are charged or billed on a consumption-based model. Cloud computing platforms must provide mechanisms to capture usage information that enables charge back reporting and integration with billing systems.
Page
12 of 21
Page
13 of 21
Page
14 of 21
Review backup and disaster-recovery systems in light of IT security. Apart from anything else, IT security breaches can require complete application recovery. Because of the complexity of securing cloud environments, many organizations use hybrid cloud environments that include public as well as private clouds. Cloud service providers each have their own way of managing security. Sometimes, the cloud service providers security plan will conflict with your companys rules. Before you implement your security plan you need to ensure that it will complement your providers plan.
Page
15 of 21
Page
16 of 21
i. Customer Perspective Data Security: Many customers dont wish to trust their
data to the cloud. Data must be locally retained for regulatory reasons. Latency: The cloud can be many milliseconds away. Not suitable for real-time applications. Application Availability: Cannot switch from existing legacy applications. Equivalent cloud applications do not exist.
ii. Vendor Perspective 1. Service Level Agreements Security: with the businesses information and critical
IT resources outside the firewall, customers worry about their vulnerability to attack. Cloud services dependability: The complex web of interdependency that supports cloud services
Page
17 of 21
availability and performance from network availability and performance, to the availability and performance of the cloud service providers systems, and beyond, to the performance and availability of the supply chain of services that the service provider depends on cries out for suppliers who can offer greater transparency of interdependencies as well as credible service level assurances. 2. Business Models SaaS/PaaS models are challenging. Much lower upfront revenue. While customers certainly enjoy the economic and operational benefits of the off-the-shelf, standardized nature of many cloud services, this survey shows they nonetheless want greater ability to fit cloud services more tightly into the context of their specific business. Users want to maximize the leverage of their many other critical business systems in-house legacy systems and, increasingly, externally-sourced cloud services by being able to integrate across these systems. SaaS 1.0 systems that lack standardbased APIs, and are effectively islands are of diminishing value; this is why user should be include the requirement for web services APIs in definition of cloud services. 3. Customer Lock-in Customers want open/standard APIs. Need to continuously add value.
Page
18 of 21
VIII. Summary
For IT departments in larger enterprises, developing a private cloud often makes the most financial and business sense. When developing the architectural vision, an enterprise architect should bear in mind the characteristics of cloud computing as well as consider some of the organizational and cultural issues that might become obstacles to the adoption of the future state architecture. When moving ahead, decisions must be made on whether the future-state technical architecture should emphasize compatibility with the current standard or start from scratch to minimize cost. Future state systems architecture designs involve trade-offs between lower cost/operational efficiency and greater flexibility. Using an Enterprise Architecture framework can help enterprise architects navigate the tradeoffs and design a system that accomplishes the business goal.
Page
19 of 21
IX. Conclusion
Cloud computing offers real alternatives to IT departments for improved flexibility and lower cost. Markets are developing for the delivery of software applications, platforms, and infrastructure as a service to IT departments over the cloud. These services are readily accessible on a pay-per-use basis and offer great alternatives to businesses that need the flexibility to rent infrastructure on a temporary basis or to reduce capital costs. Architects in larger enterprises find that it may still be more cost effective to provide the desired services in-house in the form of private clouds to minimize cost and maximize compatibility with internal standards and regulations. If so, there are several options for future-state systems and technical architectures that architects should consider finding the right trade-off between cost and flexibility. Using an architectural framework will help architects evaluate these trade-offs within the context of the business architecture and design a system that accomplishes the business goal.
Page
20 of 21
X. Abbreviation
SaaS PaaS CapEx OpEx SOA TCO IaaS QoS Software as a Service Platform as a service Capital Expenditures Operating Expenditure Service-Oriented Architecture Total Cost of Ownership Infrastructure-as-a-Service Quality of Service
Page
21 of 21