Browse Prior Art Database

A mechanism for involving your cloud centric application

IP.com Disclosure Number: IPCOM000226431D
Publication Date: 2013-Apr-03
Document File: 9 page(s) / 124K

Publishing Venue

The IP.com Prior Art Database

Abstract

Cloud-enabled applications are existing applications originally designed for a pre-cloud environment. The application architecture often dictates specific platform requirements from a certain operating system to a supporting code library. Changes to these elements are tightly controlled. Application-level multi-tenancy and elasticity are not typically present. However, Cloud-centric applications are applications created specifically for the cloud. They typically leverage cloud-based capabilities such as multi-tenancy and automatic, elastic scaling of resources. In this disclosure, we will introduce a mechanism for involving your cloud centric application, where the application could easily built with the scale-out models including both vertical and horizontal partitions, which lead to high parallel chatty communications between service consumer, service provider, and the routing engine to be based on Service Grid.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 9

A mechanism for involving your cloud centric application

Cloud-enabled applications are existing applications originally designed for a pre-cloud environment. The application architecture often dictates specific platform requirements-from a certain operating system to a supporting code library. Changes to these elements are tightly controlled. Application-level multi-tenancy and elasticity are not typically present.

However, Cloud-centric applications are applications created specifically for the cloud. They typically leverage cloud-based capabilities such as multi-tenancy and automatic, elastic scaling of resources. They often include integrated tools, and they focus on engaging users across multiple touch points, including mobile platforms and social media.

WAP3 makes available a set of highly scalable shard services to ease the development of a cloud centric application. Among them are Elastic Data Services, Elastic Messaging Services, and Service Grid. Service Grid in particular provides an easy and scalable way to partition a large complex application into smaller pieces, to enable fine grained scaling and evolvement which are vital for the next generation Web application.

The demand of cloud centric for high throughput requires the scale-out models including both vertical and horizontal partitions, which lead to high parallel

chatty communications between service consumer, service provider, and the routing engine to be based on Service Grid.

1


Page 02 of 9

you can start small and simple with one single application, running on a language fitting its purpose, e.g. Java. While it grows its complexity to support your business, you start creating more applications instead of keep growing one big monolithic animal, aka vertical partitioning. Then you start to integrate them together (through Service Grid or Message Queue). Each application, no matter which language runtime it uses, can invoke the shared interaction services to get high productivity for creating highly interactive, contextual mobile applications. These applications' development, operation and hosting activities are well supported through a highly iterative cloud centric DevOps cycle. Some of the specific ONE application may grow very big in a very fast way (daily iterative release), you need to decompose it into smaller but chatty pieces, Service Grid will enable your application to be highly performing but in form of really loosely-coupled services, aka, horizontal partitioning of your applica...