You are on page 1of 9

Survey and comparison for Open and closed sources in cloud computing

Nadir K.Salih 1 G.K.Viju2


1

School of Computer Science and Engineering, Harbin Institute of Technology, China 2 Department of Computer Science, Karary University, Sudan
nadircom2006@gmail.com, vijugk2005@gmail.com

Abstract Cloud computing is a new technology widely studied in recent years. Now there are many cloud platforms both in industry and in academic circle. How to understand and use these platforms is a big issue. A detailed comparison has been presented in this paper focused on the aspects such as the architecture, characteristics, application and so on. To know the differences between open source and close source in cloud environment we mention some examples for Software-as-aService, Platform-as-a-Service, and Infrastructure-as-aService. We made comparison between them. Before conclusion we demonstrate some convergences and differences between open and closed platform, but we realized open source should be the best option.

Fig 1 Software as a Service (SaaS)

Keywords:-Open Source, Closed Source, SaaS, PaaS, IaaS. I. INTRODUCTION Cloud Computing is a broad term that describes a broad range of services. As with other significant developments in technology, many vendors have seized the term Cloud and are using it for products that sit outside of the common definition. In order to truly understand how the Cloud can be of value to an organization, it is first important to understand what the Cloud really is and its different components. Since the Cloud is a broad collection of services, organizations can choose where, when, and how they use Cloud Computing. In this paper we explain the different types of Cloud Computing services commonly referred to as Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS) and give some examples to compare between open and closed sources. SaaS (software-as-a-Service) [22] the capability provided to the consumer is to use the providers applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings see fig 1.

Characteristics of SaaS Like other forms of Cloud Computing, it is important to ensure that solutions sold as SaaS in fact comply with generally accepted definitions of Cloud Computing. Some defining characteristics of SaaS include [23]; Web access to commercial software Software is managed from a central location Software delivered in a one to many model Users not required handling software upgrades and patches Application Programming Interfaces (APIs) allow for integration between different pieces of software PaaS (Platform-as-a-Service) is a form of cloud computing that holds considerable potential to help enterprise developers quickly write and test customer or employee facing web applications [1]. PaaS platform has several advantages:(1) develop, test, deploy and maintain on the same integrated environment, which reduced development and maintenance costs; (2) users can seamlessly experience the software online without downloading or installing;(3) more closely integrated other online services and data; (4) built-in scalability, reliability and security;(5) improved the developer's cooperation; (6) in-depth understanding of user activity;(7) pricing based on actual usage. Current platforms tend to have its own feature, and PaaS vendors are trying to perfect their platform. Platform as a Service (PaaS) is the delivery of the computing platform, it reduces the complexity of managing underlying hardware and software layers and provides the facilities to support the complete life cycle of a web application [2]. PaaS provides a solution for offering multiple applications on the same platform thus increasing

the economy of scale and reducing complexity [3]. Even though IaaS gives access to physical resources with some software configuration, for designing new applications user requires advanced tools such as Map Reduce etc. These services constitute Platform as a Service (PaaS), offering Cloud users a development platform to build their applications. In general, PaaS includes the lower layer (IaaS) as well that is bundled with the offered service. In general, pure PaaS offers only the user level middleware, which allows development and deployment of applications on any Cloud infrastructure. As noted by Appistry.com [7], the essential characteristics that identify a Platform-as-aService solution include: Runtime framework: It represents the software stack of the PaaS model and the most intuitive aspect that comes to the mind of people when referring to Platform-as-aService solutions. The runtime framework executes enduser code according to the service level policies set by the user and the provider. Abstraction: PaaS solutions are distinguished by the higher level abstraction that they provide. Unlike IaaS solutions the focus is on delivering raw access to virtual or physical infrastructure. In the case of PaaS the focus is on the applications the Cloud must support. This means that PaaS solutions offer a way to deploy and manage applications on the Cloud rather than a bunch of virtual machines on top of which the IT infrastructure is built and configured. Automation: A PaaS environment is a bit like a swan on a pond graceful and elegant above the water, and paddling its little legs off below the water. The before mentioned abstraction provides the elegant user experience above the water, while high levels of automation provide the paddling beneath the surface. PaaS environments automate the process of deploying applications to infrastructure, configuring application components, provisioning and configuring supporting technology like load balancers and databases, and managing system change based on policies set by the user. While IaaS is known for its ability to shift capital costs to operational costs through outsourcing, only PaaS is able to slash costs across the development, deployment and management aspects of the application lifecycle. Cloud services: PaaS offerings provide developers and architects with services and APIs helping them to simplify delivering of elastically scalable and highly available Cloud applications. These services are the key differentiators among competing PaaS solutions and generally include specific component for developing applications, advanced services for application monitoring, management, and reporting. The major advantage of PaaS is the cost saving in development, deployment, and management cycle of new applications. The PaaS providers reduces risk in terms of upgrade cost of

underlying platforms and allow Cloud users to concentrate on the application development. See Fig 2.

Fig 2 platform-as-a-Services

IaaS (Infrastructure-as-a-Service) see fig 3 referred to as Resource Clouds, provide (managed and scalable) resources as services to the user in other words, they basically provide enhanced virtualization capabilities. Accordingly, different resources may be provided via a service interface: Data & Storage Clouds deal with reliable access to data of potentially dynamic size, weighing resource usage with access requirements and / or quality definition. Characteristics of infrastructure as a service includes [24]: Delivery of resources such as servers, storage and network components as a service Lower total cost of ownership Full scalability Eliminate the need for administration and maintenance of hardware Enterprise grade infrastructure for all subscribers

Fig 3 Infrastructure-as-a-Service

The remainder of this paper is organized as follows. Firstly an overview of the cloud computing services is given in section1, and then the types of software-as-aservice are discussed in section 2. The some examples of the platform-as-a-service are mentioned in Section 3, Followed by kinds of infrastructure-as-a-service in section 4. Convergences of open and closed source in cloud computing are highlighted in Section 5. Finally, conclusions and future work are presented in Section 6.

II. TYPES OF SOFTWARE AS A SERVICE There are a several kinds of application or software defined as open or closed source for example: A. Autonomy Interwoven Team site CMS Interwoven [25] is a global leader in content management solutions. Interweavers software and services enable organizations to effectively leverage content to drive business growth by improving the customer experience, increasing collaboration, and streamlining business processes in dynamic environments. Interwoven helps organizations extend and protect their brands, optimize their online presence, and provide a consistent and more engaging experience across all customer touch points. Interwoven enables organizations to optimize content to drive business growth by providing collaboration, increasing productivity, simplifying compliance and streamlining business processes across various environments. B. AxCMS.net AxCMS.net [26] is a free Enterprise Web Content Management System (CMS) based entirely on Microsoft .NET platform that dramatically simplifies complex processes involved in creating and managing high scalable and interactive web applications AxCMS.net guarantees brand and content consistency of multiple sites and in multiple languages while allowing employees and external resources to create, manage and publish web content. It helps you manage information and systems for your employees, partners and customers at any time. Increase your productivity by making use of valuable employee experiences. C. Contegro Contegro [27] is a commercial Website CMS solution for medium to large organizations that is targeted at design focused Web Design, Graphic Design and Advertising agencies looking for a high end Website CMS for their clients. Contegros key point of difference over other Website CMS systems is that it removes the developer from the website lifecycle. Allowing design focused companies to deliver functionally rich websites, without the need to employ developers for any coding. This is achieved by building in an extensive level of control within the User Interface, providing partners with all the control they need to produce functional, high end websites while providing their clients (the end-user) with total control over the management of their content within a very user friendly interface. D. Amilia CMS Software as a Service (SaaS) in the case of amilia that the amilia CMS [28] will not be installed directly on the web server, but in the amilia data center. The requirements of the domain web server are very low. amilia only requires php. amilia as SaaS brings with it many advantages. amilias functionalities and user interface based on the JavaScript DHTMLX framework and a sophisticated database management. The package comes in

two different configurations: On Demand and Enterprise. The On Demand configuration is a Software as a Service (SaaS) model, can be accessed from anywhere, and includes feature and security upgrades through the life of the contract. The Enterprise edition is deployed in the company network and can also be used with secure Internet access. E. Liferay Community Edition Liferay have certain optimism about open source and those who believe in the open source philosophy. We believe that by extending the most freedom to Liferay users, they will extend their best to us and contribute to an ever richer platform with more and more capabilities. As the world's leading open source portal platform, Liferay [29] provides a unified web interface to data and tools scattered across many sources. Within Liferay Portal, a portal interface is composed of a number of portletsselfcontained interactive elements that are written to a particular standard. Since portlets are developed independently of the portal itself, and loosely coupled with the portal, they are apparently SOA (Service- Oriented Architecture). F. AdaptCMS Lite AdaptCMS [30] is a content management system (CMS) written in PHP, using a MySQL database. AdaptCMS is open source and released under the GNU General Public License. With AdaptCMS you can manage any type of content website with an advanced sections feature, custom fields, easily editable templates, an advanced permissions area and more that makes AdaptCMS adaptable to any website. G. mojoPortal MojoPortal [31] [32] is an open source, crossplatform, content management system (CMS) for ASP.NET which is written in C# programming language. The CMS supports plug-in and has built-in support for, among others, forums, blogs, photo galleries, and an ecommerce feature. The project was awarded an Open Source Content Management System Award by Packt in 2007 saying that the "ease of use, set of relevant tools and plugins and also the fact that it is cross platform, made it stand out above the rest". H. Bricolage Bricolage is free and open source software. It is a content management system (CMS) written in the Perl programming language .it Designed to manage workflow for large websites with many contributors [33]. We can conclude the comparison between closed and open software-as-a-service at the follow: 1- Software is protected by copyrights and is sold to users to earn money, while in open source paradigm; the software is available to users freely to use and to change it. 2- Development of a software is a systematic and formal work that is performed by skilled and expert developers to enhance the quality; and a centralized management team support it to improve software in new release, while in

open system model there is frequent release that software improved by users and developers around the world. 3- The successful issue in quality of closed source is related to centralized management while in open source the quality is from its openness because many programmers examine it and can detect bugs. 4- Security terms in open source are much better than closed source. 5- Terms of documentation and central management, there is a problem with open source rather than closed source. Due to lack of responsible person for the projects, the users should wait until the problem has been resolved in anyway. There are some comparisons between closed and open source of software-as-a-service that we mentioned see table 1 in appendix. III. TYPES OF PLATFORM-AS-A-SERVICE There are several solutions available in the PaaS market, to mention a few: I. Windows Azure The Windows Azure Platform [8], [6] consists of SQL Azure and the .NET services. The .NET services comprises of Access Control services and .NET service bus. Windows Azure is a platform with shared multitenant hardware provided by Microsoft. Windows Azure application development mandates the use of SQL Azure for RDBMS functionality, because that is the only coexisting DBMS functionality accessible in the same hardware context as the applications. J. Google App Engine Google App Engine [9], [4] is a web application hosting service. By web application, we mean an application or service accessed over the Web, usually with a web browser: storefronts with shopping carts, social networking sites, multiplayer games, mobile applications, survey applications, project management, collaboration, publishing, and all of the other things they discovering are good uses for the Web. App Engine can serve traditional website content too, such as documents and images, but the environment is especially designed for real-time dynamic applications. K. Force.com The Force.com [10] platform is the world's first Platform as a Service (PaaS), enabling developers to create and deliver any kind of business application in the cloud, entirely on-demand and without software. It's a break through new concept that is making companies radically more successful by letting them translate their ideas into applications in record time. Building, sharing, and running business applications have never been so easy. Force.com is built on the Salesforce server infrastructure, and all Force.com apps, like Salesforce CRM, are built around a central database. It will appeal to companies that subscribe

to Salesforce, are familiar with its data-centric apps, and are willing to learn its Apex programming language. Force.com presents a series of wizards and forms that can speed basic application layout and connection to outside services. It includes a Web services API thats aware of which Web services can be used by an app and provides a WSDL path to the service. A year ago, Salesforce added VisualForce, a user interface builder based on Adobes Flex components. With these tools, app builders can connect to their Salesforce CRM and other applications, extract data, and build database triggers that update various tables as events occur. L. Manjrasoft Aneka Aneka [5] is a platform for deploying Clouds developing applications on top of it. It provides a runtime environment and a set of APIs that allow developers to build .NET applications that leverage their computation on either public or private clouds. One of the key features of Aneka is the ability of supporting multiple programming models that are ways of expressing the execution logic of applications by using specific abstractions. The flexibility of Aneka has been demonstrated by using the framework in different scenarios: from scientific research, to educational teaching, and to industry. A set of case studies representing the success stories of Aneka has been reported to demonstrate that Aneka is mature enough to address real life problems used in a commercial environment. M. Red Hat OpenShift Red Hat OpenShift [11] redefines the PaaS market, by providing a new level of choice in languages, frameworks, and clouds for developers to build, test, run, and manage their applications. Building on Red Hat's history of supporting Java EE, OpenShift is the first PaaS to run CDI applications and plans support for Java EE 6, extending the capabilities of PaaS to even the richest and most demanding applications. Building on Red Hat's open source leadership, OpenShift ends the lock-in of PaaS, allowing developers to choose the cloud provider upon which their application will run. N. VMware VMware [12] says the distinguishing features of the Cloud Foundry platform include the fact that it is built to be multi-cloud, to work between private and public environments, and the fact that it is built to work with a wide variety of application frameworks and development tools. In terms of revenue stream, VMware has plans to offer a commercial version of Cloud Foundry for enterprises who want to offer PaaS capabilities within their own private clouds, and for service providers who want to offer Cloud Foundry via their public cloud services. This commercial solution will enable enterprises to integrate the PaaS environment with their application frameworks and services portfolio, VMware say. Pricing information has not yet been released. O. TioLive

TioLive [13] the Open Source Platform as a Service (PaaS) and ERP/CRM Software as a Service (SaaS), announced the release of TioLive Grid. With TioLive Grid, everyone can now run on his own servers a Private Cloud or a Community Cloud at no license cost. TioLive Grid aims at giving more freedom to customers and offers total control over sensitive business data. TioLive Grid is the first step towards Distributed Cloud Computing, a new approach to Cloud Computing which will eventually replace over the next years legacy Centralized Cloud Computing solutions controlled by proprietary SaaS vendors. P. WSO2 Stratos WSO2 [14] today announced the debut of WSO2 Stratos, the first 100% open source cloud platform for enterprise applications. WSO2 Stratos offers organizations of all sizes a fully hosted application platform-as-a-service (PaaS). Using WSO2 Stratos, IT professionals can build and deploy applications and services with instant provisioning of enterprise servers, including the portal, Enterprise Service Bus (ESB), and application server. WSO2 Stratos is available today as an early adopter release for private clouds, as a demonstration version on public clouds, and as an early release of the downloadable open source software. As a fully open source solution WSO2 Stratos does not require any licensing fees. Platform as a Service (PaaS) offers the potential to democratize web development by enabling anyone who can use a browser to assemble and extend web-based applications. Yet early PaaS players have introduced PaaS solutions that are remarkably proprietary, introducing high switching costs to move data or logic from one PaaS provider to another. In contrast, an Open-source Platform as a Service (OPaaS) solution leverages industry standards and allows applications to be deployed across multiple cloud providers. An OPaaS solution has four characteristics: 1. Open source - the OPaaS solution is available as open source and supported by a large open source community. 2. Portable - developers can deploy OPaaS applications on multiple cloud infrastructures, including public and private clouds. 3. Open server platform - developers must be able to use standard languages and existing code within the OPaaS. 4. Extensible client platform - developers and end users must have standard, easy-to-use tools for configuring OPaaS user interface. Although this features and other likes good security and low cost in open source platform, but it didnt developed like closed platform. See table 2 in appendix compared these two types of platform. VI. TYPES INFRASTRUCTURE-AS-A-SERVICE For infrastructure-as-a-Service there are a lot of closed and open types. We can take some examples like:

Q. Agathon Group Agathon Group [15] ("Agathon Group") is intended to help enhance the use of the Internet by preventing unacceptable use. All users of Agathon Group's Internet services ("Services")those who access some of their Services but do not have accounts ("Visitors") as well as those who pay a monthly service fee to subscribe to the Services. R. Amazon EC2 Amazon Web Services (AWS) [16] provides a flexible, cost-effective, scalable, and easy to use cloud computing platform for businesses of all sizes. With AWS, companies can requisition compute power, storage, and other services in minutesgaining access to a suite of elastic IT infrastructure services as their business needs too. Using AWS, companies have the flexibility to choose whichever development platform or programming model makes the most sense for the problems theyre trying to solve. Companies only pay for what is used, with no up-front expenses or long-term commitments, making AWS a costeffective way to deliver applications. S. Cisco Ciscos [17] long-term vision is an open, public cloud network called the inter-cloud. It involves a long-term market transition marked by ubiquitous portable workloads and a rich cloud environment in which external and internal clouds share resources. The inter-cloud will allow secure and transparent movement of resources based on available capacity, power cost, and proximity to promote a new wave of innovation. T. IBM With IBM IaaS [18], you have the capability to provision processing, storage, networks, and other computing resources, where you can deploy and run arbitrary software such as operating systems and applications. Most use cases for cloud computing follow the same fundamental layering structure you are already used to: a software solution stack or platform is deployed on a network infrastructure, and applications are run on top of the platform. However, virtualization makes the cloud paradigm unique U. Eucalyptus The Eucalyptus [19] [20] [21] system is built to allow administrators and researchers the ability to deploy an infrastructure for user-controlled virtual machine creation and control atop existing resources. Its hierarchical design targets resource commonly found within academic and laboratory settings, including but not limited to small- and mediumsized Linux clusters, workstation pools, and server farms. Eucalyptus system has filled an important niche in the cloud-computing design space by providing a system that is easy to deploy atop existing resources, that lends itself to experimentation by being modular and open

source, and that provides powerful features out-of-the-box through an interface compatible with Amazon EC2. V. Open Nebula OpenNebula [20] [21] has been designed to be modular in order to allow its integration with as many different hypervisors and environments as possible. It assumes that the physical Infrastructure adopts a classical cluster-like architecture with a front-end, and a set of host nodes where VMs will execute. There is at least one physical network joining all the cluster nodes with the front-end. The front-end executes the main OpenNebula processes while the cluster nodes are hypervisor enabled hosts that provide the resources needed by the VMs. OpenNebula works with administrative and client accounts. Administrators access OpenNebula through Command Line Interface (CLI), while clients launch and manage VMs using web services interfaces. OpenNebula implements an interface compatible with the EC2 Query API from Amazon and another one compatible with the Open Cloud Computing Interface from the Open Grid Forum. W. Reservoir Reservoir [33] has defined a Reference Architecture for a next generation of Infrastructure as a Service (IaaS) Clouds capable of dealing with new requirements such as service-orientation (services managed as a whole, automating the services provisioning and scalability, and guaranteeing Service Level Agreements), separation between infrastructure and services, use of Open/Standard specifications, virtualization technology independent, support for site federation, which allows private, public and hybrid Clouds, security and isolation reinforcement and use of utility computing business models. Reservoirs technology solution and spin-outs are available in open source code. X. Nimbus Nimbus [21] leaves most of the customization to the administrator components include the image storage, (previously GridFTP and now Cumulus), the use of Globus credentials for all user authentication, and the requirement that the running Nimbus process can cleanly Secure SHell SSH into all compute nodes. Similarly, while Nimbus is very flexible in the number and types of virtual networks that can be set up, the underlying physical mechanism for doing so is much less flexible, (at least as of this writing), and involves a DHCP server on each compute node with Nimbus choosing a random MAC address. And not to the user and has several more components which are constants. The performances of all services depend of the performances of the infrastructure provided by the cloud. Cloud computing performances depend of different parameters such as the CPU speed, the amount of memory, network and hard drive speed. In virtual environment the hardware is shared between virtual machines. And open source have some features like:

1- Datacenter operators can quickly and easily build cloud services within their existing infrastructure to offer ondemand, elastic cloud services. Additional tools simplify Administration, Security, and Billing. 2- Open source Infrastructure-as-a-Service (IaaS) software platform, which enables users to build, manage and deploy compute cloud environments. There are some characteristics as the same in closed source see table 3 in appendix. V. CONVERGENCES AND DIFFERENCES Some cloud service providers use open-source software or platforms, the base systems are usually proprietary. However, there are a few entirely open-source based platforms, as well as applications and tools available to manage mainly IaaS cloud services. These tools allow the user to monitor, manage and control the virtual instances. Unfortunately, most open-sources are at the IaaS or PaaS level and very few SaaS open-source applications exist. We found from aforementioned comparison some convergences between open and closed source like: 1- The languages can be the same in two sources 2- Application support and compatibility. 3- Using of web services 4- The type of operating system. 5- Other features like monitoring Although this convergences but the important thing stand against closed system it is the services costing. In addition the security issue can the best in open source because the control with user or organization. For this two things the future will be own to open source. VI. CONCLUSIONS This paper compares the two closed source development model and open source model for cloud computing. The result shows that in terms of costing is better to use open source methodology, rather than closed source, while there is a problem with documentation and design of using open source model, because of using novice volunteers and make a useless documentation. Also we have found out what the convergences and differences of closed source software and open source. In future we want to make a model that used open source in three layers of service in cloud computing SaaS, PaaS, and IaaS .To be full control by user and measure performance and quality of services. REFERENCES

1.
2.

AdaptCMS http://en.wikipedia.org/wiki/AdaptCMS Amazon Web Services Overview Amilia-http://en.wikipedia.org/wiki/Amilia Bhaskar Prasad Rimal, Admela Jukan, Dimitrios Katsaros, Yves Goeleven. Architectural Requirements for Cloud Computing Systems: An Enterprise Cloud Approach, Springer Science Business Media B.V, 2010.

3. 4.

5.

Charrington, S. 2010, Characteristics of Platform as a Service, Cloud Pulse blog, http://Cloudpulseblog.com/2010/02/the essentialcharacteristics-of-paas. Christian Vecchiola, Xingchen CHU, Rajkumar Buyya. Aneka: A Software Platform for .NET-based Cloud Computing, The University of Melbourne, Australia, 2009 Cloud computing service models, Part 1: Infrastructure as a Service. Contegro Review D. Chappell, Introducing the Windows Azure Platform, David Chappell & Associates, October 2010. Dan Sanderson .Programming Google App Engine. Google Press.2010 Sunil Soman, Lamia Youseff, Dmitrii Zagorodnov. The Eucalyptus Open-source Cloud-computing System. International Symposium on Cluster Computing and the Grid. IEEE, 2009.

27. http://www.readwriteweb.com/cloud/2011/08/red-hat-expandsopenshift-plat.php? utm_source=feedburner&utm_medium=feed&utm_campaign=Feed %3A+readwriteweb+(ReadWriteWeb).

6.
7. 8. 9. 10.

28. https://www.tiolive.com/news-tiolive-grid-debut.
29. Interwoven Overview

30. Jonas X. Yuan. Liferay Portal 6 Enterprise Intranets.PACKT, 2010 31. Lerner, Reuven. At the Forge - Publishing with Bricolage, Linux
Journal, 2007.

11. Daniel Nurmi, Rich Wolski, Chris Grzegorczyk ,Graziano Obertelli, 12. Dedicated 13. Gen-Tao

32. Microsoft Azure. www.microsoft.com/windowsazure/


33. 34. 35. 36. MojoPortal New to AxCMS.net Open Source TioLive Innovates with Distributed Cloud Computing Model ahead of Proprietary PaaS Leaders. Peter Sempolinski, Douglas Thain. A Comparison and Critique of Eucalyptus, OpenNebula and Nimbus. 2nd IEEE International Conference on Cloud Computing Technology and Science. IEEE, 2010. Application Development in the Cloud, salesforce.com, 2010

Cloud Computing Services and Infrastructure as a Servicehttp://www.expedient.com/products/iaas.php Chiang, Martin T. Dove, C. Isabella Bovolo, and John Ewen. Implementing a Grid/Cloud eScience Infrastructure for Hydrological Sciences. Springer-Verlag London Limited, 2011. http://62.149.240.97/index.php?page=technical-information

14. Google App Engine. http://code.google.com/appengine/.


15.

37. Phil Choi ,Chris McGuire, Caroline Roth. An Introduction to Custom 38. Red Hat Expands OpenShift Platform as a Service with Java EE6 and
39. 40. 41. Membase Reservoir: Resources and Services Virtualization without Barriers. The Information Technology Security Council (ITSC) and Physical Security Council (PSC). Cloud Computing and Software as a Service (SaaS), ASIS International, 2010. Thiago Cordeiro, Douglas Damalio, Nadilma Pereira, Patricia Endo, Andre Palhares, Glauco Gonalves, Djamel Sadok, Judith Kelner, Bob Melander, Victor Souza, Jan-Erik Mangs. Open Source Cloud Computing Platforms. 2010 Ninth International Conference on Grid and Cloud Computing. IEEE, 2010. http://broadcast.rackspace.com/hosting_knowledge/whitepapers/Unde rstanding-the-Cloud-Computing-Stack.pdf Virtualized Multi-Tenant Data Center Solution for Infrastructure-asa- Service Unveils Open Source PaaS Cloud Foundry http://www.infoq.com/news/2011/04/VMWare-Cloud-Foundry WSO2 launches WSO2 Stratos Open Source Cloud Computing Platform for Enterprise Application Development. International Conference on Networking and Distributed Computing. IEEE, 2010

16. http://d36cz9buwru1tt.cloudfront.net/AWS_Overview.pdf 17. http://help.axcms.net/en_new_to.AxCMS 18. http://media.corporateir.net/media_files


/irol/11/115270/corp_pro_5_07.pdf

19. http://wso2.com/about/news/wso2-launches-wso2-stratos-opensource-cloud-computing-platform-for-enterprise-applicationdevelopment/

20. http://www.adaptcms.com/page/38/Support/ 21. http://www.agathongroup.com/hosting/aup/


22. http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ ns836/white_paper_c11-604559.pdf.

42. Understanding the Cloud Computing Stack: SaaS, PaaS, and IaaS.
43.

23. http://www.cmscritic.com/contegro-review/ 24. http://www.ibm.com/developerworks/cloud/library/clcloudservices1iaas/

44. VMware
45.

25. http://www.informationweek.com/blog/main/archives/2009/01/mojop
ortal_a_so.html .

26. http://www.packtpub.com/article/mojoportal-wins-best-other-opensource-content-management-system .

46. Z. Shu-Qing, Xu Jie-Bin. The Improvement of PaaS Platform, First

Platform Supported

Autonomy Interwoven Teamsite CMS Perl, Java Oracle, SQL Server, DB2

AxCMS.net

Contegro

amilia CMS

Liferay Community Edition Java HSQLDB, MySQL, Oracle, SQL Server, DB2, Apache Derby, Informix, InterBase, JDataStore yes Liferay .com Open

AdaptCMS Lite PHP MySQL

mojoPortal

Bricolage

ASP.NET SQL Server

ASP.NET SQL Server

PHP MySQL

ASP.NET SQL Server, MySQL, PostgreSQL, SQLite, Firebird, SQLCE

Perl on mod_perl MySQL, PostgreSQL

Web management Software provider Software type

Yes Interwoven TeamSite Closed

Yes Axinom Closed

Yes Kiwi CMS Closed

Yes Amilia Corporation Inc Closed

yes Charlie Page's Open

yes Packt Open

yes Salon.com, Open

Appendix
Windows Azure Service type OS support Deployment language User access interface Compatibility Web and none web application Windows Visual Studio, and .Net C#, C++, Microsoft windows azure portal with the Microsoft app Google App Engine Web app Windows or Linux Python, java Force.com Web services Apex Apex Manjrasoft Aneka Compute/data ,Web and non-web apps Linux, Windows Java Red Hat OpenShift Web app Linux java EE VMware Simplified infrastructures Linux, Windows PHP,java TioLive Web app GNU/Linux java WSO2 Stratos SOA middleware services Linux, Window PHP,java

Web-based administration console Amazon's EC2, S3

Adobes Flex

Workbench, webbased portal Amazons EC2, Xen

Command line. GUI. Amazon EC2

vSphere Web

ERP5

Command line. GUI Amazon's EC2, Eucalyptus, Ubuntu Enterprise Cloud Open WSO2

Amazons EC2

Eucalyptus, Amazon's EC2

Amazon EC2, Gpars

Source type Owner

closed Microsoft

Closed Google

Closed salesforce.com

Closed Manjrasoft

Open Red Hat

Open VMware Inc

Open Nexedi

Table1 comparison of open and closed source in Software-as-a-Service

Table2 comparison of open and closed source in platform-as-a-Service

Agathon Group Provider OS Agathon Group Gentoo,Linux,Wi ndows server 2008

Amazon EC2

Cisco

IBM

Eucalyptus

OpenNebula

Reservoir

Nimbus

Amazon EC2 Gentoo,Linux,Window s

Cisco CentOS, ,Linux, Windows server 2008 -

IBM

Eucalyptus Cent OS

OpenNebula Linux,Open solaris,open SUSE

Reservoir Linux

Melia Technolog ies Microsoft Windows XP/Vista

Red Hat Enterprise Linux SUSE Linux all the programm ing languages Yes Yes Web Based Applicatio n/Control Panel,API Closed

Language Supported Monitorin g Web Service Control Interface

Java Java, Perl, PHP, Yes, Free No Web Based Application/ Control Panel Open Yes, Free No Web Based Application/ Control Panel Open

PHP, XMLmosaic No Yes, Free API (Application Programming Interface) Closed

Java,php,python,ruby, WinDev Yes free No API (Application Programming Interface),command line Closed Yes free Yes, Free Web Based Application/ Control Panel Closed

Java, Perl, PHP,SAS,SQ L Yes, Free Yes, Free API (Application Programming Interface) Open

HTML

yes yes Web Services based Open

Source type

Table3 comparison of open and closed source in Infrastructure-as-a-Service

You might also like