DOCSLIB.ORG

Design of a Platform of Virtual Service Containers for Service Oriented Cloud Computing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Design of a Platform of Virtual Service Containers for Service Oriented Cloud Computing DESIGN OF A PLATFORM OF VIRTUAL SERVICE CONTAINERS FOR SERVICE ORIENTED CLOUD COMPUTING Carlos de Alfonso Andrés García Vicente Hernández INDEX • Introduction • Our approach • Platform design • Storage • Security • Management and QoS • Catalogue • User Interface • Virtual Container • User profiles • Working lines and open problems 2 INTRODUCTION • In the latter years there have been a growing interest in Cloud Computing technologies and its possible applications. • There have appeared many commercial products • Mainly storage and Infrastructure as a Service. • Storage examples: Amazon S3, Nirvanix, Savvis • IaaS examples: Amazon EC2, GoGrid, 3Tera • Other examples: Google App Engine, Salesforce, Engine Yard • Some small sets of open Cloud Computing tools have been also developed. • Eucalyptus, Nimbus, OpenNebula, Enomaly, Abicloud, etc. • Almost any of them are oriented to the IaaS level, since there is a lack of research projects towards other cloud approaches. 3 INTRODUCTION • Currently most of cloud computing solutions are focusing in the lowest levels of the infrastructure. • Virtual machine deployment and management infrastructure. • Storage management infrastructure. • The current approach of vendors, to deploy Services in the cloud, is based in those levels instead of Services virtualization. • Provider’s approach is to package a preconfigured service in a virtual machine image, and deploy a whole virtual appliance to run the service. • There are some drawbacks like the waste of resources, a less direct service management, the low abstraction level, etc. OUR APPROACH • To offer a platform which enable developers to deploy and to manage virtual services as IaaS platforms deploy and manage virtual machines. • That means to deploy only the service instance that is needed, instead of deploying the whole virtual appliance. • Allow consumers to search and use services in a Software as a Service basis. • Usage on demand, access via internet, scalability, monitoring, etc. • Provide the platform administrators with a transparent security model, and a framework to define QoS constraints and SLA with developers and consumers. • Including mechanisms such as authentication and authorization, user preferences, usage limits, etc. 5 PLATFORM DESIGN • The platform is composed by a set of interconnected functional modules and two abstraction layers. • An abstraction layer is conceived as an Interface used by the components, independently of the underlying implementation. • A module is defined as an individual software component that can be instanced, added or removed to the platform. • A platform instance is formed by at least one instance of each module. • Each module implements a specific functionality. • Modules interact with each other via messages. 6 PLATFORM DESIGN • The following diagram outlines the general architecture of the platform components. • Vertical boxes represent layers, not directly a implementing component. • Horizontal boxes represents system components. 7 LAYERS: STORAGE • A virtual storage layer provides a set of features. • Ubiquitous access to data. • Any service should be able to read any data independently of where the service is running or where the data is stored (under the scope of the platform). • Virtualized file system. • Final users do not care about where to store data. • Users are provided with a virtual uniform file system, even if files are stored in physically distributed places • Isolation. • Users are only able to read and write what they are authorized to. • Data management, replication and QoS. • Need to ‘move the data where the problem is’ or to ‘deploy the problem where the data is’. • Need to replicate or move data to improve resilience and QoS. • Need to be done transparently via SLA and developer directives. • Different implementations are to be made, to couple this virtual layer to the physical system where the data will be stored. • Usage of GridFTP. • Connection to the Amazon S3 system. • Just the local hard drive. 8 LAYERS: SECURITY • The platform makes use of a default security system. • Any users, either administrators, developers or consumers are identified by a credential. • The credential provides authentication and it is used for authorization. • Each user identity is bound to a set of preferences, SLA and storage. • Credentials enable developers to deploy services, manage them and negotiate QoS agreements with the platform. • Credentials enable consumers to search and use deployed services in a private virtual space, having access only to their own personal service instance. • Credential delegation allows service composition and cloud interoperability. 9 COMPONENTS: MANAGEMENT AND QOS • The “Management and Quality of Service” component provides the functionality to deploy and to manage services while maintaining a reasonable quality of service of the platform. • The management module provide a set of functionalities. • Service deployment, to deploy copies of the service bundle in a set of Virtual containers. • Service undeployment from the Virtual containers, keeping alive the running service instances until they finish. • Upgrade services to new versions, so that the new service requests will get an instance of the new service, and not the old one. The downtime is minimized by using an upgrade protocol. • Live migration, for undeploying a service from a virtual containers and deploying it into another one, minimizing the downtime and keeping running instances alive. • Using the “live migration” ability, it provides load balancing and auto scale based in a certain criteria. • Developers can attach a SLA to each service, based on its own base SLA, to specify parameters such as minimum number of replicas, geographical constraints in the deployment place, etc. 10 COMPONENTS: MANAGEMENT AND QOS • The QoS module provides resilience and avoids the degradation of the service quality. • The QoS module monitors the state of the platform and performs actions to improve the general performance. • Live service migration and service replication allows load balancing. • Replication of platform components provides resilience. • The Interoperability module complements the QoS module. • When the platform cannot meet the requirements of its SLA due to overload, components failures, etc., it can negotiate with other clouds the rent of resources. • Platforms will negotiate based on their own platform credentials, SLA, the resources required and a internal policy set by the system administrators. 11 COMPONENTS: CATALOGUE • The Catalogue stores information about the state of the platform as a whole. • Each module provides the Catalogue with specific information about different aspects of the platform, sending status reports periodically. • Services: Provide information about services, their name, developer, description and a reference to the resource itself. Service consumers use this catalogue via the User Interface in order to get access to the services. • Metrics: Provides a ‘snapshot’ of the platform state e.g. number of components, number of services, active service images, service CPU consumption, etc. • Statistics: Provides long term information about the platform and its services e.g. usage info for services. 12 COMPONENTS: CATALOGUE • The Catalogue component work as a peer-to-peer distributed hierarchical system. • Inspired by existing P2P discovery models for Grid systems. • Catalogues are organized in groups, associated to a platform, and each catalogue has only a partial state of the group. • A query must be distributed to every member on the group in a P2P basis. • Catalogue groups are organized hierarchically, and queries in a group must be distributed to their child groups. • Queries to one member of a group are broadcasted to the whole group. • Each module reports its status to a set of n catalogues, using a hash algorithm. • This organization provides resilience capabilities and improves the QoS. • There are no single points of failure, implements a load balancing between nodes. • Hierarchical organization of the catalogues may enable a logical association of clouds. • Several private clouds can be federated in a ‘top level cloud’. • Defining such top level catalogue group would allow users to access services in a semi-centralized way. 13 COMPONENTS: USER INTERFACE • The UI is the entry point to the whole platform, which provides consumers and developers with different functionalities, according to the profile and needs. • It acts as a platform front-end, connecting external users and applications to the other components. • This component does not implement any functionality per-se, but calls other components to perform different tasks. • Query the catalogue for information. • Deploy, undeploy and manage services. • Define user parameters or preferences. • Etc. 14 COMPONENTS: VIRTUAL CONTAINER • Virtual containers are the key component of the Virtual Service Platform. • This component run and give access to the virtualized services. • A Virtual Container is a regular service container with additional functionality such as functions to deploy, undeploy and migrate services, as well as statistics and metrics tracking and a security framework to fit the platform. • The virtual containers make use of most of the components outlined in previous slides. • Virtual Containers define what kind of virtual services support our platform. 15 USER PROFILES • Developers can deploy services in the platform written in any supported language, provided that it is instrumented with the platform
Load more

Recommended publications
  • Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community
    Deliverable No. 5.3 Techniques to build the cloud infrastructure available to the community Grant Agreement No.: 600841 Deliverable No.: D5.3 Deliverable Name: Techniques to build the cloud infrastructure available to the community Contractual Submission Date: 31/03/2015 Actual Submission Date: 31/03/2015 Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Grant Agreement no. 600841 D5.3 – Techniques to build the cloud infrastructure available to the community COVER AND CONTROL PAGE OF DOCUMENT Project Acronym: CHIC Project Full Name: Computational Horizons In Cancer (CHIC): Developing Meta- and Hyper-Multiscale Models and Repositories for In Silico Oncology Deliverable No.: D5.3 Document name: Techniques to build the cloud infrastructure available to the community Nature (R, P, D, O)1 R Dissemination Level (PU, PP, PU RE, CO)2 Version: 1.0 Actual Submission Date: 31/03/2015 Editor: Manolis Tsiknakis Institution: FORTH E-Mail: [email protected] ABSTRACT: This deliverable reports on the technologies, techniques and configuration needed to install, configure, maintain and run a private cloud infrastructure for productive usage. KEYWORD LIST: Cloud infrastructure, OpenStack, Eucalyptus, CloudStack, VMware vSphere, virtualization, computation, storage, security, architecture. The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement no 600841. The author is solely responsible for its content, it does not represent the opinion of the European Community and the Community is not responsible for any use that might be made of data appearing therein.
    [Show full text]
  • Cloud Computing: a Taxonomy of Platform and Infrastructure-Level Offerings David Hilley College of Computing Georgia Institute of Technology
    Cloud Computing: A Taxonomy of Platform and Infrastructure-level Offerings David Hilley College of Computing Georgia Institute of Technology April 2009 Cloud Computing: A Taxonomy of Platform and Infrastructure-level Offerings David Hilley 1 Introduction Cloud computing is a buzzword and umbrella term applied to several nascent trends in the turbulent landscape of information technology. Computing in the “cloud” alludes to ubiquitous and inexhaustible on-demand IT resources accessible through the Internet. Practically every new Internet-based service from Gmail [1] to Amazon Web Services [2] to Microsoft Online Services [3] to even Facebook [4] have been labeled “cloud” offerings, either officially or externally. Although cloud computing has garnered significant interest, factors such as unclear terminology, non-existent product “paper launches”, and opportunistic marketing have led to a significant lack of clarity surrounding discussions of cloud computing technology and products. The need for clarity is well-recognized within the industry [5] and by industry observers [6]. Perhaps more importantly, due to the relative infancy of the industry, currently-available product offerings are not standardized. Neither providers nor potential consumers really know what a “good” cloud computing product offering should look like and what classes of products are appropriate. Consequently, products are not easily comparable. The scope of various product offerings differ and overlap in complicated ways – for example, Ama- zon’s EC2 service [7] and Google’s App Engine [8] partially overlap in scope and applicability. EC2 is more flexible but also lower-level, while App Engine subsumes some functionality in Amazon Web Services suite of offerings [2] external to EC2.
    [Show full text]
  • Envisioning the Cloud: the Next Computing Paradigm
    Marketspace® Point of View Envisioning the Cloud: The Next Computing Paradigm March 20, 2009 Jeffrey F. Rayport Andrew Heyward Research Associates Raj Beri Jake Samuelson Geordie McClelland Funding for this paper was provided by Google, Inc Table of Contents Executive Summary .................................................................................... i Introduction................................................................................................ 1 Understanding the cloud...................................................................... 3 The network is the (very big, very powerful) computer .................... 6 How the data center became possible ............................................. 8 The passengers are driving the bus ...................................................11 Where we go from here......................................................................12 Benefits and Opportunities in the Cloud ..............................................14 Anywhere/anytime access to software............................................14 Specialization and customization of applications...........................17 Collaboration .......................................................................................20 Processing power on demand...........................................................21 Storage as a universal service............................................................23 Cost savings in the cloud ....................................................................24 Enabling the Cloud
    [Show full text]
  • Multi-Tenant, Secure, Load Disseminated Saas Architecture
    Multi-Tenant, Secure, Load Disseminated SaaS Architecture Zeeshan Pervez, Sungyoung Lee Department of Computer Engineering, Kyung Hee University, South Korea {zeeshan, sylee}@oslab.khu.ac.kr Abstract – The availability of high speed internet has diversified Leading companies in information technology industry are the way we used to intermingle with each other. The emergence gradually moving their applications and related data over the of social networks and interactive web applications has left a internet and delivering them through SaaS [2]. Google has dent in existing software and service delivery models. Software used SaaS platform to offer web applications for vendors now not only focus on functionality but also have to communication and collaboration [3], gradually replacing cater delivery model of their software. On-demand and ubiquitous accessibility has become an inimitable selling point recourse exhaustive desktop applications. Similarly Microsoft for software vendors. In the last few years we have witnessed a is offering their development and database services though term “Cloud computing” thronging blogs and search engines. SaaS platform codename Microsoft Azure [4]. SaaS is Cloud computing is on-demand service delivery; services preached by the companies like SalesForce.com, 3Tera, ranging from Infrastructure, Platform and Software. With the Microsoft, Zoho and Amazon, as a result of which business materialization of Amazon Cloud Computing Service we have specific services can be consumed in ubiquitous environment. seen exponential increase in interest of business as well as research community in Cloud computing Orchestra. Now 2. MULTI-TENANT ARCHITECTURE: technological oracles are offering their software in Cloud as Software as a Service (SaaS). Every service provider is laying on SaaS not only has altered the software delivery model, but line to gain competitive advantage over each other, there is need it also had amended the way in which software is developed.
    [Show full text]
  • Cloud Computing What Is Cloud Computing?
    Cloud Computing What is Cloud Computing? • Cloud Computing is a general term used to describe a new class of network based computing that takes place over the Internet, – basically a step on from Utility Computing – a collection/group of integrated and networked hardware, software and Internet infrastructure (called a platform). – Using the Internet for communication and transport provides hardware, software and networking services to clients • These platforms hide the complexity and details of the underlying infrastructure from users and applications by providing very simple graphical interface or API (Applications Programming Interface). 2 What is Cloud Computing? • In addition, the platform provides on demand services, that are always on, anywhere, anytime and any place. • Pay for use and as needed, elastic – scale up and down in capacity and functionalities • The hardware and software services are available to – general public, enterprises, corporations and businesses markets 3 Cloud Summary • Cloud computing is an umbrella term used to refer to Internet based development and services • A number of characteristics define cloud data, applications services and infrastructure: – Remotely hosted : Services or data are hosted on remote infrastructure. – Ubiquitous : Services or data are available from anywhere. – Commodified : The result is a utility computing model similar to traditional that of traditional utilities, like gas and electricity - you pay for what you would want! 4 Cloud Architecture 5 What is Cloud Computing • Shared pool
    [Show full text]
  • TECHNOLOGY TOOLS of Thetrade
    TECHNOLOGY TOOLS of theTRADE ATX Tax use. You can view demos of all have USB 2.0 retractable con- Programs the packages online and request nectors that open and retract At the center of the family of an evaluation kit. While check- with a twist, and both are back- tax offerings for individual and ing the ATX demos at the site, wards-compatible with USB 1.1. business tax preparers, there’s preview the ATX Scan&Fill soft- The high-speed transfer rates ware with Document Manager. are up to 480MBits per second, With these you can scan W-2s and the drives are compatible and 1099s, exporting the num- with Windows 2000, XP, and bers directly into your return. Vista, as well as Mac OS X v. Print and store PDF versions of 10.3.5 or higher. The coins are a the final return with the pro- little under 1.5 inches wide and gram’s Document Manager. about a third of an inch thick. apply so you can finish your www.atxinc.com Each drive comes with a USB return in less than one hour. A extension cable. CurrenKey new Audit Support Center offers ATX™ MAX®. Within the MAX LaCie CurrenKey drives were designed for step-by-step guidance on every- group of offerings there’s MAX; USB Flash Drives LaCie by 5.5 Designers. thing you need to know in the MAX for Business; Total Tax Be sure to keep the archived www.lacie.com event you are contacted by the Office, which includes Klein- copies of your clients’ records IRS.
    [Show full text]
  • Galvin's All Things Enterprise
    Galvin’s All Things Enterprise The State of the Cloud, Part 2 PETER BAER GALVIN Peter Baer Galvin is the CTO In the previous edition of Galvin’s All Things Enterprise, cloud was the center of for Corporate Technologies, attention . In spite of the over-hyping and frequent under-delivery of cloud, it’s still a premier systems integrator an important, new, and evolving area of computing and, therefore, worth some and VAR (www.cptech. discussion and analysis . The first task was defining cloud computing, and the next com). Before that, Peter was the systems was exploring “why cloud”—what does cloud computing bring to the table and why manager for Brown University’s Computer should you care? Science Department. He has written articles This column continues the analysis by giving examples of projects that have and columns for many publications and is successfully used cloud computing . Why did they succeed when others have failed, co-author of the Operating Systems Concepts and what did they gain by using cloud technologies? Of course there are reasons to textbooks. As a consultant and trainer, Peter avoid cloud computing, and those are included as well . The column finishes with teaches tutorials and gives talks on security a comprehensive list of cloud considerations—what you should consider when and system administration worldwide. Peter is determining if a given project should be based on cloud technologies, and whether also a Lecturer at Boston University and Senior it would be best implemented in a public cloud, a private cloud, or a hybrid cloud, or Contributor to BYTE.
    [Show full text]
  • Cloud Computing and Security Speaker
    Introducing Data Management (a Cloud Service) David Cohen, Architect and Senior Technologist Cloud Infrastructure Group EMC Corporation Data Storage as a Service (DaaS) (the delivery of virtualized storage on demand) Type Presentation Consumable (1) Object REST (or SOAP) via HTTP Blob (2) Distributed File System CIFS, NFS, WebDAV, FTP, etc File System (e.g. export, share, etc) (3) Block Device (used to SCSI (or ATA) over IP Volume suitable for provide local file use in Volume system) Manager (4) Tabular REST via HTTP Table (5) Relational Product specific SQL Database (6) Messaging AMQP Store‐and‐Forward Queue or Topic‐based Publish/Subscriber Definitions 1. Resource ‐ Often referred to as a “server,” this is a composition of I/ O, RAM, and CPU. 2. Resource Pool ‐ A container of lots of servers. 3. Customer – Procures resources for a specific use. 4. Service Provider – The steward of the underlying resource pool; invoicing the customer on a subscription/usage basis. 5. Cloud Computing – Resources are dynamically provisioned from a shared pool. This provisioning operation is initiated by the customer over a network via a self-service Portal. Service Models (1) Deployment Model (Mell et al, “The NIST Definition of Cloud Computing,” 2009) Type Location Relationship (1) Private Customer Premise Central IT (2) Public Service Provider Premise 3rd party (3) Community Service Provider Premise (n) customers/(1) 3rd party; sharing (4) Hybrid Both Federation of Central IT and 3rd Party (2) Platform Model (Mell et al, “The NIST Definition of Cloud
    [Show full text]
  • Cloud Management
    Cloud Management A PEEK INTO WHAT REAL USERS THINK 2015 IT Central Station helps tech professionals by providing... A comprehensive list of A sample of real user Specific information to help enterprise level Cloud reviews from tech you choose the best vendor Management vendors. professionals. for your needs. Disclaimer IT Central Station Ltd. does not endorse or recommend any products or services. The views and opinions of reviewers quoted in this document, IT Central Station websites, and IT Central Station materials (i.e. Content) do not reflect the opinions of IT Central Station. We make no guarantees about the accuracy, currency, suitability, or quality of the content, and we assume no responsibility for unintended, objectionable, inaccurate, misleading, or unlawful content made available by Content authors or other third parties. © 2015 IT Central Station Reproduction Prohibited To read more reviews about Cloud Management, please visit: http://www.itcentralstation.com/category/cloud-management ABOUT IT CENTRAL STATION User reviews, candid discussions, and more for enterprise technology professionals. The Internet has completely changed the way we make buying decisions. We now use ratings and review sites to see what other real users think before we buy Use IT Central Station to: electronics, book a hotel, visit a doctor or choose a restaurant. But in the world of enterprise technology, • Read and post reviews of vendors most of the information online and in your inbox comes and products from vendors but what you really want is objective • Request or share information about information from other users. functionality, quality, and pricing • Contact real users with relevant We created IT Central Station to provide product experience technology professionals like you with a • Get immediate answers to questions community platform to share information about • Validate vendor claims enterprise software, applications, hardware and • Exchange tips for getting the best services.
    [Show full text]
  • Cloud Computing Series
    Systems Engineering at MITRE CLOUD COMPUTING SERIES A Decision Process for Applying Cloud Computing in Federal Environments Geoffrey Raines Lawrence Pizette March 2010; Revised August 2010 Executive Summary an initial cloud service concept through to imple- mentation, that clarifies and defines the key deci- Commercial industry’s use of cloud computing, sion information required and contemporary cloud leveraging economies of scale, commoditizing pro- options. This paper defines an engineering decision cessing power and storage, and incrementally leas- process for applying cloud computing services in a ing only the information technology (IT) infrastruc- Federal Government context and explores impor- ture that is needed at a given moment, is presenting tant activities such as: a compelling business model to Federal leadership, worthy of further investigation. In considering the • Scoping a cloud capability effort application of cloud computing approaches to sup- • Determining which cloud services will benefit an port Federal IT enterprise portfolios, it is useful to organization have a structured engineering process, flowing from • Establishing a business case for cloud services Commercially-Managed Public Cloud Services (4.1) (4.2) Acquisition Activation • Create purchase orders, • Activate leased assets lease agreements • Load content • Perform competition or • Establish operations sole source • Establish performance • Negotiate Service Level monitoring Agreements Solution Scoping and Denition • Begin billing/payment • Negotiate performance process measurement methods (2.1) (2.2) (2.3) Cloud Service Service Denition Business Case Requirements • Scope the types of • Define the business • Identify cloud service services to be obtained rationale for creating or detailed requirements Government-Managed Cloud Services from the cloud moving to cloud services for the types defined in (3.0) (E.g.
    [Show full text]
  • ISACA April Cloud Computing
    A Primer on Cloud Computing By Anand Ganesan Byteonic.com Agenda • Background • Cloud Computing Defined • Taxonomy • Value Proposition • Cloud Providers • Who uses it • Opportunities for Improvement Background The Challenges • Make all New York Times archived articles from 1851 to 1922 available free of charge over the internet • 11 Million articles as images to be scanned and converted to PDF format in an inflexible project deadline Solution • Use Amazon Web Services infrastructure for reading and converting the article images to PDF Results • All 11 million articles processed in < 24 hours • Using 100 Amazon EC2 instances • The total cost ~$240 Definition Cloud Computing refers to both the applications delivered as services over the Internet and the hardware and systems software in the datacenters that provide those services. The datacenter hardware and software is what we will call a Cloud. .. Cloud Computing has the following characteristics: 1. The illusion of infinite computing resources… 2. The elimination of an up-front commitment.. 3. The ability to pay for use of computing resources.. - UC Berkeley RAD Lab SOURCE: “Above the Clouds: A Berkeley View of Cloud Computing” Feb 2009; UC Berkeley Reliable Adaptive Distributed Systems Laboratory Taxonomy Software As A Service High SaaS Platform As A Service PaaS Abstraction Public IaaS Hybrid Cloud Private Low Infrastructure As A Service Value Proposition Value 1. No infrastructure investment costs 2. Only operational costs based on usage 3. Multi-tenant architecture leads to massive economy of scale 4. Flexibility leads to increases in operational efficiency 5. No commitment Cloud Providers (Examples) 1. Salesforce 2. SuccessFactors 3. Intuit Quickbase SaaS 4.
    [Show full text]
  • Multi-Tenant, Secure, Load Disseminated Saas Architecture
    Multi-Tenant, Secure, Load Disseminated SaaS Architecture Zeeshan Pervez, Sungyoung Lee Department of Computer Engineering, Kyung Hee University, South Korea {zeeshan, sylee}@oslab.khu.ac.kr Abstract – The availability of high speed internet has diversified Leading companies in information technology industry are the way we used to intermingle with each other. The emergence gradually moving their applications and related data over the of social networks and interactive web applications has left a internet and delivering them through SaaS [2]. Google has dent in existing software and service delivery models. Software used SaaS platform to offer web applications for vendors now not only focus on functionality but also have to communication and collaboration [3], gradually replacing cater delivery model of their software. On-demand and ubiquitous accessibility has become an inimitable selling point recourse exhaustive desktop applications. Similarly Microsoft for software vendors. In the last few years we have witnessed a is offering their development and database services though term “Cloud computing” thronging blogs and search engines. SaaS platform codename Microsoft Azure [4]. SaaS is Cloud computing is on-demand service delivery; services preached by the companies like SalesForce.com, 3Tera, ranging from Infrastructure, Platform and Software. With the Microsoft, Zoho and Amazon, as a result of which business materialization of Amazon Cloud Computing Service we have specific services can be consumed in ubiquitous environment. seen exponential increase in interest of business as well as research community in Cloud computing Orchestra. Now 2. MULTI-TENANT ARCHITECTURE: technological oracles are offering their software in Cloud as Software as a Service (SaaS). Every service provider is laying on SaaS not only has altered the software delivery model, but line to gain competitive advantage over each other, there is need it also had amended the way in which software is developed.
    [Show full text]