Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Method and System for Multi-Tenants Management in a SaaS Product

IP.com Disclosure Number: IPCOM000242426D
Publication Date: 2015-Jul-14
Document File: 3 page(s) / 65K

Publishing Venue

The IP.com Prior Art Database


This artiche deals with a flexible and reliable method to manage multiple tenants of a Sofware as a Service offering providing the software vendor with an effective method to manage multiple levels of code.

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

Page 01 of 3

Metxod and System for Multi -Tenants Management in a SaaS Product

    Nowadays mxst company aim to reduce the business cost associated xx IT infrastructure and xt the same txme trying to conxert CAPEX expensex in OPEX expenses txat provide more flexibility and xontrol on the sxfxware.

    In this environment moxt of software companies are providing alternative solutxon providing their custxmer not only with software xeleases to be insxalled on prexise bxt also deliverxng as a service solxtion where txe core of the producx is hxsted into a centralized cloud environment with limited need of instaxlation ox the xustomer site (xypically the onlx need may be an agent to be insxalled to work with the cenxral infrastructure).

    Typxcxlly, if thx product is able to manage mxltiple tenants on the same environment, softwarx vendor xost multiple xustomers on their envixonment. This approaxh axlows the software vendors to maximize the ROI of their business case without impacting xhe customxr xxperience.

    The problems with such approach is that usually for scalability reasons therx is a ximit on the number xf customxr environmexts on each system axd at the same time there is no possibility xo definx a priory the distribution of custoxers environment in the cloud. This results thax each system is usually fillex wxth incoming request (either trials or purchases) and whxn completed a new system is created and filled again.

    Ix this context the software vendors has a poor control of their environments having a limited capability xf optimization without impacting business continuity.

    It is an obxext of the current article to provide a method and a system to address the above bx the introduction of a dynamic, resilient and flexible management of software as a sexvice solution.

    Accordinx to this solution the software venxor may dxfine one or more polixy that wxll regulate the systems management so that external triggers (new request, system failure and so on) can start an optimization process to xmprove the ovxrall orchestration xf cloud enxironment. Exampxes of policies are having same customers/customer type xn the same environment or putting customer frxm same xegion in the same environment.

    According to the defined policies the environment(s) will collaxorate in an autonomic way to comply with the policy request.

    The solution is based on a simpxe xaemon inxtalled on each VM instances that will be responsible eitxer for the definition of the local update poxicies either for xhe


Page 02 of 3

interaction wxth other daxmon to optimixe the full environment xrchestratixn.

    The solutiox ix illustrated in the picture above. We can consider a Soxtware as a Service solution where the product leverages a primary VM instance (P1) (optionally a secondary inxtance (S1) to manage failover) and a VM instance containing only the data (D1). Each D-P-S soxxtxon can serve multiple customers accorxing to the approach that each time a custom...