Browse Prior Art Database

A Method for porting Tenant instances across Multi Tenant SaaS applications in cloud

IP.com Disclosure Number: IPCOM000241525D
Publication Date: 2015-May-08
Document File: 5 page(s) / 49K

Publishing Venue

The IP.com Prior Art Database

Abstract

Cloud based enterprise applications that are being offered as software as a service, typically are configured with multi-tenancy. When a tenant running their custom application, runs into bug or a problem, the fix typically requires applying it on the underlying application, which will affect all the tenants. It will not be acceptable for tenants to have such an outage. A new method of serialization /deserialization layer that facilitates send and receive of tenants without bringing the application down is described. Serialization/deserilization layer sits on top of the application, and provides necessary framework to send/receive tenants in a serialized way. How the framework needs to be implemented, what are the components involved and how it transfers tenants from one application instance to another, are covered.

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

Page 01 of 5

A Method for porting Tenant instances across Multi Tenant SaaS applications in cloud

     Cloud based enterprise applications that are being offered as software as a service, typically are configured with multi-tenancy. Multi-tenancy involves multiple tenants sharing the same application, but have their own data and run-time context in their own container. So each tenant will maintain their own customized behavior as per their requirements. So when a tenant running their custom application, runs into bug or a problem, the fix typically requires applying it on the underlying application, which will affect all the tenants. Applying the fix will involve downtime of the application and which means all the tenants in production will have to be stopped. It will not be acceptable for tenants to have such an outage.

     Today there is no serialization/deserialization layer available to receive and send tenants while they are running to another application instance. In this disclosure we have come up with a new method of serialization /deserialization layer that facilitates send and receive of tenants without bringing the application down.

     Therefore there is a need for a method to deliver a bug fix or release upgrade to a tenant without effecting the rest of the tenants running on the same application. One need not have to stop the entire application for updating a tenant specific behavior.

     The proposed implementation of serialization / deserialization layer on the application running as software as a service will help us achieve solution to the problem. There will be sender and receiver processes to transfer the tenant run-time context data and configuration data across applications. The details are mentioned in the description.

     The method described here makes the porting of the tenant specific customization easily manageable without interrupting the other tenants interaction with the application.

There is a need to have a Serialization and Deserialization layer on the application which comprises of a sender and receiver.


Sender : The sender is a process on the serialization/ deserialization layer which can serialize a tenant run time context and configuration data from the source application running on cloud and then transfer it to the updated target application.


Receiver : The receiver is a process on the serialization/ deserialization layer which can receive the serialized tenant instance, then deserialize it and then mount on the target application.


The serialization/ deserialization layer ensures appropriate communication between the sender process and receiver process. Each application that is being

1


Page 02 of 5

developed for cloud should have this serialization/deserialization layer to cater to the need of sending and receiving tenants.


In the below diagram, the application is running as software as a service in the cloud. It supports multi tenancy. There are four tenant instances of the application running simultaneously...