# US 2020/0394061 A1 · System and method for an efficient and scalable multitenant database implementation for services platforms, including cloud services platforms

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0394061 A1
- Document ID: US20200394061A1
- Status: Published application
- Kind: A1
- Application number: 16/438,708
- Filed: 2019-06-12
- Published: 2020-12-17
- Earliest claimed: 2019-06-12
- Assignees: Open Text Corporation
- Applicants: Open Text Corporation
- Inventors: Dhatchana Moorthy Sekar
- Web page: https://patentgrep.com/patent/US20200394061A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 16/252: {between a Database Management System and a front-end application}
- G06F 16/213: {with details for schema evolution support}
- G06F 2009/45562: {Creating, deleting, cloning virtual machine instances}
- G06F 2009/45587: {Isolation or security of virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments of a services application on web services platform that employs embodiments of a database architecture for use in multitenant environments that replicates the same schema in the context of a database are disclosed. These schemas can be accessed using a database access object corresponding to the database and a particular schema for a particular tenant. In particular, the object identifier used to access the objects of the schema may be algorithmically generated based on the tenant.

## Claims

### Claim 1

A web services system, comprising:
a multitenant web services application deployed on a web services platform;
a database layer, comprising a database;
a non-transitory computer readable medium, comprising instructions for:
establishing a first schema in the database for a first tenant of the web services application;
establishing a second schema in the database for a second tenant of the web services application, wherein the first schema is a replica of the second schema;
in response to receiving a first request from a first user at a first client application:
determining that the first request is associated with the first tenant;
based on the determination that the first request is associated with the first tenant, establishing a first session at the web service application, the first session associated with the first client application;
establishing a first database connection object configured to access the first schema of the database; and
associating the first database connection object with the first user session;
in response to receiving a second request from a second user at a second client application:
determining that the second request is associated with the second tenant;
based on the determination that the second request is associated with the second tenant, establishing a second session at the web service application, the second session associated with the second client application;
establishing a second database connection object configured to access the second schema of the database; and
associating the second database connection object with the second user session;
receiving a third request at the web services application;
determining if the third request is associated with the first tenant or the second tenant;
based on a determination that the third request is associated with the first tenant, performing the third request by accessing the first schema in the database associated with the first tenant using the first session and first database connection object associated with the first schema; and
based on a determination that the third request is associated with the second tenant, performing the third request by accessing the second schema in the database associated with the second tenant using the second session and second database connection object associated with the second schema.

### Claim 2 (depends on 1)

The system of claim 1, wherein determining that the first request is associated with the first tenant comprises determining that the first user of the first client application is associated with the first tenant using user authentication credentials for the first user.

### Claim 3 (depends on 2)

The system of claim 2, wherein the third request is a request to create an object and wherein the instructions are for:
establishing a first range of sequence numbers associated with the first tenant and a second range of sequence numbers associated with the second tenant; and
creating an object identifier for the object, where the object identifier includes a number in the first range of sequence numbers when it is determined that the third request is associated with the first tenant and the object identifier includes a number in the second range of sequence numbers when it is determined that the second request is associated with the second tenant.

### Claim 4 (depends on 3)

The system of claim 3, wherein determining if the third request is associated with the first tenant or the second tenant is based on user credentials associated with the third request.

### Claim 5 (depends on 4)

The system of claim 4, wherein the first user session includes a first identifier for the first tenant and the second user session includes a second identifier for the second tenant.

### Claim 6 (depends on 5)

The system of claim 5, wherein determining if the third request is associated with the first tenant or the second tenant comprises associating the third request with the first user session or the second session.

### Claim 7

A method, comprising:
establishing a first schema in a database for a first tenant of a multitenant web services application deployed on a web services platform;
establishing a second schema in the database for a second tenant of the web services application, wherein the first schema is a replica of the second schema;
in response to receiving a first request from a first user at a first client application:
determining that the first request is associated with the first tenant;
based on the determination that the first request is associated with the first tenant, establishing a first session at the web service application, the first session associated with the first client application;
establishing a first database connection object configured to access the first schema of the database; and
associating the first database connection object with the first user session;
in response to receiving a second request from a second user at a second client application:
determining that the second request is associated with the second tenant;
based on the determination that the second request is associated with the second tenant, establishing a second session at the web service application, the second session associated with the second client application;
establishing a second database connection object configured to access the second schema of the database; and
associating the second database connection object with the second user session;
receiving a third request at the web services application;
determining if the third request is associated with the first tenant or the second tenant;
based on a determination that the third request is associated with the first tenant, performing the third request by accessing the first schema in the database associated with the first tenant using the first session and first database connection object associated with the first schema; and
based on a determination that the third request is associated with the second tenant, performing the third request by accessing the second schema in the database associated with the second tenant using the second session and second database connection object associated with the second schema.

### Claim 8 (depends on 7)

The method of claim 7, wherein determining that the first request is associated with the first tenant comprises determining that the first user of the first client application is associated with the first tenant using user authentication credentials for the first user.

### Claim 9 (depends on 8)

The method of claim 8, wherein the third request is a request to create an object and wherein the method further comprises:
establishing a first range of sequence numbers associated with the first tenant and a second range of sequence numbers associated with the second tenant; and
creating an object identifier for the object, where the object identifier includes a number in the first range of sequence numbers when it is determined that the third request is associated with the first tenant and the object identifier includes a number in the second range of sequence numbers when it is determined that the second request is associated with the second tenant.

### Claim 10 (depends on 9)

The method of claim 9, wherein determining if the third request is associated with the first tenant or the second tenant is based on user credentials associated with the third request.

### Claim 11 (depends on 10)

The method of claim 10, wherein the first user session includes a first identifier for the first tenant and the second user session includes a second identifier for the second tenant.

### Claim 12 (depends on 11)

The method of claim 11, wherein determining if the third request is associated with the first tenant or the second tenant comprises associating the third request with the first user session or the second session.

### Claim 13

A non-transitory computer readable medium comprising instructions for:
establishing a first schema in a database for a first tenant of a multitenant web services application deployed on a web services platform;
establishing a second schema in the database for a second tenant of the web services application, wherein the first schema is a replica of the second schema;
in response to receiving a first request from a first user at a first client application:
determining that the first request is associated with the first tenant;
based on the determination that the first request is associated with the first tenant, establishing a first session at the web service application, the first session associated with the first client application;
establishing a first database connection object configured to access the first schema of the database; and
associating the first database connection object with the first user session;
in response to receiving a second request from a second user at a second client application:
determining that the second request is associated with the second tenant;
based on the determination that the second request is associated with the second tenant, establishing a second session at the web service application, the second session associated with the second client application;
establishing a second database connection object configured to access the second schema of the database; and
associating the second database connection object with the second user session;
receiving a third request at the web services application;
determining if the third request is associated with the first tenant or the second tenant;
based on a determination that the third request is associated with the first tenant, performing the third request by accessing the first schema in the database associated with the first tenant using the first session and first database connection object associated with the first schema; and
based on a determination that the third request is associated with the second tenant, performing the third request by accessing the second schema in the database associated with the second tenant using the second session and second database connection object associated with the second schema.

### Claim 14 (depends on 13)

The non-transitory computer readable medium of claim 13, wherein determining that the first request is associated with the first tenant comprises determining that the first user of the first client application is associated with the first tenant using user authentication credentials for the first user.

### Claim 15 (depends on 14)

The non-transitory computer readable medium of claim 14, wherein the third request is a request to create an object and wherein the method further comprises:
establishing a first range of sequence numbers associated with the first tenant and a second range of sequence numbers associated with the second tenant; and
creating an object identifier for the object, where the object identifier includes a number in the first range of sequence numbers when it is determined that the third request is associated with the first tenant and the object identifier includes a number in the second range of sequence numbers when it is determined that the second request is associated with the second tenant.

### Claim 16 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein determining if the third request is associated with the first tenant or the second tenant is based on user credentials associated with the third request.

### Claim 17 (depends on 16)

The non-transitory computer readable medium of claim 16, wherein the first user session includes a first identifier for the first tenant and the second user session includes a second identifier for the second tenant.

### Claim 18 (depends on 17)

The non-transitory computer readable medium of claim 17, wherein determining if the third request is associated with the first tenant or the second tenant comprises associating the third request with the first user session or the second session.
