IP Library Granted Patent US 9,420,035
Granted Patent B2
US 9,420,035 · App. 14/185,898 · Granted Aug 16, 2016

Transaction isolation during multi-tenant transaction requests

Inventors: Paul Michael Evans (Portland, OR); Paul Fredric Klein (Newbury Park, CA)
Assignee: International Business Machines Corporation
H04L67/10G06F9/46G06F9/5005G06F21/6236G06Q30/00H04L67/1002
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,420,035
App. No.
14/185,898
Granted
Aug 16, 2016
Kind
B2
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 (40)

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;

a non-transitory computer system readable medium including program instructions executed by the at least one processor to perform:

receiving a transaction request from a tenant device;

identifying a tenant identifier from the tenant device;

instantiating each of an isolated chain of pluggable components from at least one memory module;

associating the instantiated isolated chain of pluggable components with the identified tenant identifier;

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

releasing access to the instantiated 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 tenant 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 the 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 the releasing the 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 associating the isolated chain of pluggable components 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 in a computer system, the method comprising:

receiving the transaction request from a tenant module;

identifying a tenant identifier from the tenant module;

instantiating in a non-transitory computer readable storage media each of an isolated chain of pluggable components from at least one memory module;

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

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

releasing access to the instantiated 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 tenant 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 the 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 the releasing the 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 associating the isolated chain of pluggable components with the tenant identifier prevents commingling with another isolated chain of pluggable components.

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

receive the transaction request from a tenant module;

identify a tenant identifier from the tenant module;

instantiate each of an isolated chain of pluggable components from at least one memory module;

associate the tenant identifier with the instantiated isolated chain of pluggable components;

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

release access to the instantiated 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 the 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 the releasing the 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 associating the isolated chain of pluggable components with the tenant identifier prevents commingling with another isolated chain of pluggable components.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2014
From: EVANS, PAUL MICHAEL; KLEIN, PAUL FREDRIC
To: INTERNATIONAL BUSINESS MACHINES CORPORATION
Reel/Frame 032261/0114 →
Continuity (1)
Related Publication 20150235014A1 · Aug 20, 2015