Enabling multi-tenant access to respective isolated data sets organized using different application schemas

• US 10,387,387 B2
• Filed: 12/17/2015
• Issued: 08/20/2019
• Est. Priority Date: 12/17/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Lam, Yu Jun, Busuioc, Laurentiu, Huang, Yongran, Maurya, Anand, Ondrejka, Peter, Nyakas, Laszlo, Parent, Kyle I., Juvara, Paolo, Park, Wansoo
• Primary Examiner(s): Hutton, Nan
• Application Number:
  US14/973,256
• Publication Number:
  US 20170177625A1
• Time in Patent Office: 1,342 Days
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/213 with details for schema evolution support
• CPC Class Codes: G06F 16/24553 of query operations

Abstract

Multi-tenant access to respective isolated data sets organized using different application schemas is disclosed. Multiple tenants store respective data sets in separate datastores. The datastores are organized using different application schemas, each derived from a same base schema. However, the tenants share access to a same application. The application receives a first request from a first tenant and a second request from a second tenant. The application serves the first request by accessing a first data set organized using a first application schema. The application serves the second request by accessing a second data set using a second application schema.

Claims

1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising:

receiving, by an application from a first tenant, a first request for accessing a first data set stored in a first datastore organized according to a first application schema derived from a base schema;

transmitting, by the application to the first tenant, a first response comprising at least a subset of the first data set;

receiving, by the application from a second tenant, a second request for accessing a second data set stored in a second datastore organized according to a second application schema derived from the base schema, the second application schema being different than the first application schema;

transmitting, by the application to the second tenant, a second response comprising at least a subset of the second data set;

wherein the first datastore is associated with the first tenant and the second datastore is associated with the second tenant;

wherein the first datastore and the second datastore are associated with a same physical database, and a cache of the physical database performs caching for both the first datastore and the second datastore;

wherein at least one of the first datastore and the second datastore comprises a pluggable database;

wherein a first update for the base schema is applied to the first application schema and is applied to the second application schema, and a second update for the first application schema is not applied to the base schema and is not applied to the second application schema.

2. The medium of claim 1, wherein the operations further comprise:

prior to transmitting the first response;

generating, by the application, the first response by executing a first set of operations that are selected based on the first application schema; and

prior to transmitting the second response;

generating, by the application, the second response by executing a second set of operations that are selected based on the second application schema, the second set of operations being different than the first set of operations.

3. The medium of claim 2, wherein the first request and the second request are substantially similar.

4. The medium of claim 1, wherein the first application schema includes references to a different number of data fields than the second application schema.

5. The medium of claim 1, wherein the first datastore is associated with a first type of data structure, and wherein the second datastore is associated with a second type of data structure different than the first type of data structure.

6. The medium of claim 1, wherein the operations further comprise:

receiving an update for the base schema; and

applying the update for the base schema to each of the first application schema and the second application schema.

7. The medium of claim 1, wherein the operations further comprise:

receiving an update for the first application schema from the first tenant; and

applying the update to the first application schema without modifying either of the second application schema or the base schema.

8. The medium of claim 1, wherein each of the first datastore and the second datastore comprises a separate pluggable database.

9. The medium of claim 1, wherein the first datastore comprises a first data structure of a particular database instance, and wherein the second datastore comprises a second data structure of the particular database instance.

10. The medium of claim 1, wherein:

the first application schema includes references to a different number of data fields than the second application schema;

the first datastore comprises a first data structure of a particular database instance, and the second datastore comprises a second data structure of the particular database instance;

the operations further comprise;

prior to transmitting the first response;

generating, by the application, the first response by executing a first set of operations that are selected based on the first application schema;

prior to transmitting the second response;

generating, by the application, the second response by executing a second set of operations that are selected based on the second application schema, the second set of operations being different than the first set of operations, and the first request and the second request being substantially similar;

receiving a first update for the base schema;

applying the first update for the base schema to each of the first application schema and the second application schema;

receiving a second update for the first application schema from the first tenant; and

applying the second update to the first application schema without modifying either of the second application schema or the base schema.

11. The medium of claim 1, wherein a first caching policy of the first datastore and a second caching policy for the second datastore are different.

12. A method comprising:

receiving, by an application from a first tenant, a first request for accessing a first data set stored in a first datastore organized according to a first application schema derived from a base schema;

transmitting, by the application to the first tenant, a first response comprising at least a subset of the first data set;

receiving, by the application from a second tenant, a second request for accessing a second data set stored in a second datastore organized according to a second application schema derived from the base schema, the second application schema being different than the first application schema;

transmitting, by the application to the second tenant, a second response comprising at least a subset of the second data set;

wherein the first datastore is associated with the first tenant and the second datastore is associated with the second tenant;

wherein the first datastore and the second datastore are associated with a same physical database, and a cache of the physical database performs caching for both the first datastore and the second datastore;

wherein at least one of the first datastore and the second datastore comprises a pluqqable database;

wherein a first update for the base schema is applied to the first application schema and is applied to the second application schema, and a second update for the first application schema is not applied to the base schema and is not applied to the second application schema.

13. The method of claim 12, further comprising:

prior to transmitting the first response;

generating, by the application, the first response by executing a first set of operations that are selected based on the first application schema; and

prior to transmitting the second response;

generating, by the application, the second response by executing a second set of operations that are selected based on the second application schema, the second set of operations being different than the first set of operations.

14. The method of claim 13, wherein the first request and the second request are substantially similar.

15. The method of claim 13, wherein the first request and the second request are identical.

16. The method of claim 12, wherein the first application schema includes references to a different number of data fields than the second application schema.

17. The method of claim 12, wherein the first datastore is associated with a first type of data structure, and wherein the second datastore is associated with a second type of data structure different than the first type of data structure.

18. The method of claim 12, further comprising:

receiving an update for the base schema; and

applying the update for the base schema to each of the first application schema and the second application schema.

19. The method of claim 12, wherein each of the first datastore and the second datastore comprises a separate pluggable database.

20. A system comprising:

at least one hardware device including a processor; and

the system configured to perform operations comprising;

receiving, by an application from a first tenant, a first request for accessing a first data set stored in a first datastore organized according to a first application schema derived from a base schema;

transmitting, by the application to the first tenant, a first response comprising at least a subset of the first data set;

receiving, by the application from a second tenant, a second request for accessing a second data set stored in a second datastore organized according to a second application schema derived from the base schema, the second application schema being different than the first application schema;

transmitting, by the application to the second tenant, a second response comprising at least a subset of the second data set;

wherein the first datastore is associated with the first tenant and the second datastore is associated with the second tenant;

wherein the first datastore and the second datastore are associated with a same physical database, and a cache of the physical database performs caching for both the first datastore and the second datastore;

wherein at least one of the first datastore and the second datastore comprises a pluqqable database;

wherein a first update for the base schema is applied to the first application schema and is applied to the second application schema, and a second update for the first application schema is not applied to the base schema and is not applied to the second application schema.