TRANSACTION ISOLATION DURING MULTI-TENANT TRANSACTION REQUESTS

• US 20150235014A1
• Filed: 02/20/2014
• Published: 08/20/2015
• Est. Priority Date: 02/20/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Klein, Paul Fredric, Evans, Paul Michael
• Granted Patent: US 9,420,035 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6236 between heterogeneous systems
• CPC Class Codes: G06F 9/46 Multiprogramming arrangements
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers

Abstract

Described is a multi-tenant Software as a Service (SaaS) computing environment which provides at least one logical server where two or more sets of tenant data can be processed by the logical server to keep the data from commingling with each other. To prevent data commingling, every tenant transaction request is isolated, via the described system and method, from all other tenant transaction requests by dynamically creating and later destroying unique pluggable components that satisfy the transaction requests.

Claims

1. A computing system for transaction isolation during a software as a service transaction request of a networked computing environment, the computing system comprising:

at least one processor receiving a transaction request from a tenant device, wherein the processor identifies a tenant identifier from the tenant device;

at least one memory module including an isolated chain of pluggable components, the isolated chain of pluggable components being associated with the tenant identifier;

at least one processor executing instructions to process each component of the isolated chain of pluggable components in a sequence to satisfy the transaction request; and

the at least one memory module releasing access to the isolated chain of pluggable components after the satisfaction of the transaction request.

2. The computing system of claim 1, wherein the tenant identifier is a unique identifier.

3. The computing system of claim 1, wherein the isolated chain of pluggable components includes an instance of at least one template component.

4. The computing system of claim 3, wherein the at least one template component can be instantiated as a plurality of pluggable components in the one memory module such that each of the plurality of pluggable components is associated with a unique tenant identifier.

5. The computing system of claim 1, wherein the isolated chain of pluggable components does not interact with another isolated chain of pluggable components.

6. The computing system of claim 3, wherein a released isolated chain of pluggable components prevents access to the instance of at least one template component by another transaction request.

7. The computing system of claim 1, wherein the isolated chain of pluggable components being associated with the tenant identifier prevents commingling with another isolated chain of pluggable components.

8. A computer implemented method for transaction isolation during a transaction request, the method comprising:

receiving the transaction request from a tenant module;

identifying a tenant identifier from the tenant module;

associating the tenant identifier with an isolated chain of pluggable components;

processing each component of the isolated chain of pluggable components in a sequence to satisfy the transaction request; and

releasing access to the isolated chain of pluggable components after the satisfaction of the transaction request.

9. The method of claim 8, wherein the tenant identifier is a unique identifier.

10. The method of claim 8, wherein the isolated chain of pluggable components includes an instance of at least one template component.

11. The method of claim 10, wherein the at least one template component can be instantiated as a plurality of pluggable components such that each of the plurality of pluggable components is associated with a unique tenant identifier.

12. The method of claim 8, wherein the isolated chain of pluggable components does not interact with another isolated chain of pluggable components.

13. The method of claim 10, wherein a released isolated chain of pluggable components prevents access to the instance of at least one template component by another transaction request.

14. The method of claim 8, wherein the isolated chain of pluggable components being associated with the tenant identifier prevents commingling with another isolated chain of pluggable components.

15. A computer program product for transaction isolation during a transaction request, the computer program product including one or more computer-readable storage modules and program instructions stored on at least one of the one or more storage modules, the program instructions comprising:

program instructions to receive the transaction request from a tenant module;

program instruction to identify a tenant identifier from the tenant module;

program instruction to associate the tenant identifier with an isolated chain of pluggable components;

program instructions to process each component of the isolated chain of pluggable components in a sequence to satisfy the transaction request; and

program instructions to release access to the isolated chain of pluggable components after the satisfaction of the transaction request.

16. The computer program product of claim 15, wherein the isolated chain of pluggable components includes an instance of at least one template component.

17. The computer program product of claim 16, wherein the at least one template component can be instantiated as a plurality of pluggable components such that each of the plurality of pluggable components is associated with a unique tenant identifier.

18. The computer program product of claim 15, wherein the isolated chain of pluggable components does not interact with another isolated chain of pluggable components.

19. The computer program product of claim 16, wherein a released isolated chain of pluggable components prevents access to the instance of at least one template component by another transaction request.

20. The computer program product of claim 15, wherein the isolated chain of pluggable components being associated with the tenant identifier prevents commingling with another isolated chain of pluggable components.