Service-Oriented Cloud Computing Architecture(SOCCA)

Authors: Wei-Tek Tsai, Xin Sun, Janaka BalasooriyaSeventh International Conference on Information Technology

12-14 April 2010, Las Vegas, NV

Presented By: Junaid Haseeb

Outline

• Introduction

•Problem Statement

•Proposed Solution(SOCCA)

•Advantages

•Disadvantages

•Conclusion

Cloud Computing

Clouds have emerged as a computing infrastructure that enables rapid delivery of computing resources as a utility in a dynamically scalable, virtualized manner.

Service Oriented Architecture(SOA)

SOA is an architectural pattern that guides business solutions to create, organize and reuse its computing components.

SOA Allows application components to provide services to other components via communications protocol.

Existing Cloud Architectures

Both academia and industry have been active on cloud computing research and proposed several architectures.

•Reservior- IBM [1]

•Aneka- .Net based PaaS Cloud solution [2]

•Market oriented cloud architecture used by Aneka [3]

• Service oriented Cloud computing platform for web-delivery of application-based services- IBM [4]

Problem Statement

Issues with current cloud implementations include

• Lack of interoperability among cloud providers

• Lack of Multi-tenancy support

•Application development across multiple Clouds

Service-Oriented Cloud Computing Architecture (SOCCA)

Multi-tenancy Architecture (MTA)

Multi-tenancy is an architecture in which a single instance of a software application serves to multiple customers.

Three different multi-tenancy patterns available in SOCCA.

• Single Application Instance(SAI)

•Multiple Application Instance(MAI)

• Single Application Instance and Multiple Service Instances(SAIMSI)

Multi-tenancy Patterns

Application Development on SOCCA

Service Package, Source Code, Configuration File, Resource File

Initial Prototype and Experiment

Requirement: When each user visits the web page, he/she will be greeted by a random message retrieved from a motto database.

1- Application using Google App Engine is developed in which a number of mottos are retrieved and stored from and to Google cloud by using Data store with JDO.

Initial Prototype and Experiment

2. A web service is created that wraps the Azure SQL service that allows retrieving and storing mottos from the motto databases deployed on Azure.

3. Web Service Connector (WSC) tool is used to generate Google App Engine compatible client code in java to access the web service deployed in step 2.

4.Created a class that implements “javax.jdo.PersistenceManagerFactory” which is the interface GAE Data store uses to manipulate the data on the cloud.

5. An instance is created SQLPersistenceManagerFactory that implements “javax.jdo.PersistenceManagerFactory”.

Initial Prototype and Experiment

6. A code snippet shows that depending on the config file, the application will be connected with either GAE Datastore database or Azure SQL database.

Advantages

•A new multi tenancy pattern Single application instance and multiple service instances (SAIMSI) becomes possible with SOCCA.

• SOCCA allows an application to run on other clouds and interoperate with each other.

• SOCCA supports easy migration of applications from one cloud to another.

• SOCCA provides better support for cloud’s multi-tenancy feature.

Disadvantages

• SOCCA does not provide any modeling language to map different language sets as different clouds supports different language sets.

• Instance for the same service cannot live on multiple clouds.

Conclusion

• The SOCCA is a 4-layer architecture that supports both SOA and cloud computing.

• SOCCA allows an application to run on different clouds, migration of applications and interoperate with each other.

• SOCCA provides high support of multi-tenancy feature of Cloud.

• SOCCA allows application development across multiple Clouds.

References

Tsai, Wei-Tek, Xin Sun, and Janaka Balasooriya. "Service-oriented cloud computing architecture." Information Technology: New Generations (ITNG), 2010 Seventh International Conference on. IEEE, 2010.