IP Library Granted Patent US 11,546,307
Granted Patent B2
US 11,546,307 · App. 17/235,275 · Granted Jan 3, 2023

Method to implement multi-tenant/shared Redis cluster using envoy

Inventors: Aniruddha Kulkarni (Bangalore, IN); Shivansh Rai (Bangalore, IN); Dhatri Bidarahalli (Bangalore, IN)
Assignee: SAP SE
H04L63/0428H04L63/0281H04L63/102H04L67/10
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 11,546,307
App. No.
17/235,275
Granted
Jan 3, 2023
Kind
B2
Abstract

A system and method are disclosed associated with at least one physical data store instance adapted to contain electronic records; and a shared cluster platform, coupled to the data store, including: a computer processor, and a computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor cause the shared cluster platform to: receive a request for a first tenant; select a physical data store instance in response to the request; generate a first container for the first tenant, wherein the first container maps the first tenant to the selected physical data store instance; generate a unique first key element for the first tenant; and transmit a first endpoint of the first container as a proxy for the selected physical data store instance, wherein the transmission fulfills the request. Numerous other embodiments are provided.

Claims (59)

1. A system associated with a multi-tenant data store, comprising:

at least one physical data store instance adapted to contain electronic records; and

a shared cluster platform, coupled to the data store, including:

a computer processor, and

a computer memory, coupled to the computer processor, storing instructions that, when executed by the computer processor cause the shared cluster platform to:

receive a request for a first tenant;

select a physical data store instance in response to the request;

generate a first container for the first tenant, wherein the first container maps the first tenant to the selected physical data store instance;

generate a unique first key element for the first tenant; and

transmit a first endpoint of the first container as a proxy for the selected physical data store instance, wherein the transmission fulfills the request.

2. The system of claim 1 , wherein the first key element is transmitted with each data request for the first user.

3. The system of claim 1 , wherein the first tenant is a user of an application adapted to receive the transmitted first endpoint of the first container.

4. The system of claim 1 , further comprising instructions to:

generate an authorization password for the first tenant; and

transmit the authorization password and the first key element.

5. The system of claim 1 , further comprising instructions to:

receive a second request for a second tenant;

select the physical data store instance mapped to the first tenant in response to the request;

generate a second container for the second tenant, wherein the second container maps the second tenant to the selected physical data store instance;

generate a unique second key element for the second tenant; and

transmit a second endpoint of the second container as a proxy of the selected physical data store instance, wherein the transmission fulfills the second request.

6. The system of claim 1 , wherein the physical data store instance is received from a data store provider.

7. The system of claim 6 , further comprising instructions to:

request a second physical data store instance from the data store provider in a case a threshold value is met.

8. The system of claim 1 , wherein the first endpoint is a host name and Internet Protocol (IP) address of the first container.

9. The system of claim 1 , wherein the unique first key element is a random string.

10. A computer-implemented method associated with a multi-tenant data store, comprising:

selecting a physical data store instance;

generating a first container for a first tenant, wherein the first container maps the first tenant to the selected physical data store instance;

generating a unique first key element for the first tenant;

generating an authorization password for the first tenant; and

transmitting a first endpoint of the first container as a proxy for the selected physical data store instance.

11. The computer-implemented method of claim 10 , wherein the first key element is transmitted with each data request for the first tenant.

12. The computer-implemented method of claim 10 , further comprising:

transmitting the authorization password and the first key element.

13. The computer-implemented method of claim 10 , further comprising:

receiving a request for a second tenant;

selecting the physical data store instance mapped to the first tenant;

generating a second container for the second tenant, wherein the second container maps the second tenant to the selected physical data store instance;

generating a unique second key element for the second tenant;

transmitting a second endpoint of the second container as an proxy of the selected physical data store instance, wherein the transmission fulfills the request.

14. The computer-implemented method of claim 10 , wherein the physical data store instance is received from a data store provider.

15. The computer-implemented method of claim 14 , further comprising:

requesting a second physical data store instance from the data store provider in a case a threshold value is met.

16. The computer-implemented method of claim 10 , wherein the first endpoint is a host name and Internet Protocol (IP) address of the first container.

17. The computer-implemented method of claim 10 , wherein the unique first key element is a random string.

18. A non-transitory, computer readable medium having executable instructions stored therein to perform a method associated with a multi-tenant data store, the medium comprising:

instructions to receive a request for a first tenant;

instructions to select a data store instance based on the request;

instructions to generate a first container for the first tenant, wherein the first container maps the first tenant to the selected data store instance;

instructions to generate a unique first key element for the first tenant; and

instructions to transmit to a first endpoint of the first container as a proxy for the selected data store instance.

19. The medium of claim 18 , further comprising:

instructions to receive a second request for a second tenant;

instructions to select the physical data store instance mapped to the first tenant;

instructions to generate a second container for the second tenant, wherein the second container maps the second tenant to the selected physical data store instance;

instructions to generate a unique second key element for the second tenant; and

instructions to transmit a second endpoint of the second container as a proxy of the selected physical data store instance, wherein the transmission fulfills the second request.

20. The medium of claim 18 , wherein the first endpoint is a host name and Internet Protocol (IP) address of the first container.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 20, 2021
From: KULKARNI, ANIRUDDHA; RAI, SHIVANSH; BIDARAHALLI, DHATRI
To: SAP SE
Reel/Frame 055975/0867 →
Continuity (1)
Related Publication 20220337561A1 · Oct 20, 2022
Cited By (1)
US 12,333,041