Plug and play multi tenancy support for cloud applications
One embodiment is related to a method for setting a tenant context for an application in a multi-tenancy environment, comprising: identifying a tenant identity for a tenant request, wherein the tenant identity is included in the tenant request; and setting a proper context for a first service of the application based on the identified tenant identity.
1. A method for setting a tenant context for an application in a multi-tenancy environment, comprising:
identifying, by a multitenancy support module, a tenant identity of a tenant for a tenant request subsequent to a successful authentication of the tenant, wherein the tenant identity is included in the tenant request;
setting, by the multitenancy support module, a tenant context for a first service of the application based on the identified tenant identity, wherein the application is not multitenancy-aware, wherein communication and data storage/retrieval protocols, including relational databases and in-memory database caching services, used by the first service of the application are hooked into by the multitenancy support module, and wherein the setting of the tenant context for the first service of the application comprises returning a database connection comprising a database server instance and a database schema associated with the tenant identity, wherein the setting of the tenant context for the first service further comprises returning to the first service a key value store connection comprising a key value store bucket and a key value store schema associated with the tenant identity; and
in response to the first service of the application transmitting a message to a second service of the application using a messaging protocol, passing, by the multitenancy support module, the tenant context to the second service from the first service, wherein passing the tenant context further comprises: adding, by the multi-tenancy support module, the tenant identity to the message as a header at the first service, and recovering, by the multi-tenancy support module, the tenant identity from message at the second service.
2. The method of claim 1 , wherein the tenant request comprises a hypertext transfer protocol (HTTP) message, and the tenant identity is included in the tenant request as an HTTP header.
3. The method of claim 1 , wherein the messaging protocol comprises at least one of Java Message Service (JMS) or Advanced Message Queuing Protocol (AMQP).
4. The method of claim 1 , wherein the passing of the tenant context to the second service of the application further comprises:
setting the tenant context for the second service based on the recovered tenant identity, wherein the key value store connection includes Amazon S3 “Simple Storage Service”.
5. A non-transitory machine-readable medium having instructions stored therein which, when executed by a processor, cause the processor to perform support operations, the operations comprising:
identifying, by a multitenancy support module, a tenant identity of a tenant for a tenant request within a multi-tenancy environment subsequent to a successful authentication of the tenant, wherein the tenant identity is included in the tenant request;
setting, by the multitenancy support module, a tenant context for a first service of an application based on the identified tenant identity, wherein the application is not multitenancy-aware, wherein communication and data storage/retrieval protocols, including relational databases and in-memory database caching services, used by the first service of the application are hooked into by the multitenancy support module, and wherein the setting of the tenant context for the first service of the application comprises returning a database connection comprising a database server instance and a database schema associated with the tenant identity, wherein the setting of the tenant context for the first service further comprises returning to the first service a key value store connection comprising a key value store bucket and a key value store schema associated with the tenant identity; and
in response to the first service of the application transmitting a message to a second service of the application using a messaging protocol, passing, by the multitenancy support module, the tenant context to the second service from the first service, wherein passing the tenant context further comprises: adding, by the multi-tenancy support module, the tenant identity to the message as a header at the first service; and recovering, by the multi-tenancy support module, the tenant identity from message at the second service.
6. The non-transitory machine-readable medium of claim 5 , wherein the tenant request comprises a hypertext transfer protocol (HTTP) message, and the tenant identity is included in the tenant request as an HTTP header.
7. The non-transitory machine-readable medium of claim 5 , wherein the messaging protocol comprises at least one of Java Message Service (JMS) or Advanced Message Queuing Protocol (AMQP).
8. The non-transitory machine-readable medium of claim 5 , wherein the passing of the tenant context to the second service of the application further comprises:
setting the tenant context for the second service based on the recovered tenant identity, wherein the key value store connection includes Amazon S3 “Simple Storage Service”.
9. A data processing system, comprising:
a processor; and
a memory coupled to the processor storing instructions which, when executed by the processor, cause the processor to perform support operations, the operations including
identifying, by a multitenancy support module, a tenant identity of a tenant for a tenant request within a multi-tenancy environment subsequent to a successful authentication of the tenant, wherein the tenant identity is included in the tenant request;
setting, by the multitenancy support module, a tenant context for a first service of an application based on the identified tenant identity, wherein the application is not multitenancy-aware, wherein communication and data storage/retrieval protocols, including relational databases and in-memory database caching services, used by the first service of the application are hooked into by the multitenancy support module, and wherein the setting of the tenant context for the first service of the application comprises returning a database connection comprising a database server instance and a database schema associated with the tenant identity, wherein the setting of the tenant context for the first service further comprises returning to the first service a key value store connection comprising a key value store bucket and a key value store schema associated with the tenant identity; and
in response to the first service of the application transmitting a message to a second service of the application using a messaging protocol, passing, by the multitenancy support module, the tenant context to the second service from the first service, wherein passing the tenant context further comprises: adding, by the multi-tenancy support module, the tenant identity to the message as a header at the first service; and recovering, by the multi-tenancy support module, the tenant identity from message at the second service.
10. The data processing system of claim 9 , wherein the tenant request comprises a hypertext transfer protocol (HTTP) message, and the tenant identity is included in the tenant request as an HTTP header.
11. The data processing system of claim 9 , wherein the messaging protocol comprises at least one of Java Message Service (JMS) or Advanced Message Queuing Protocol (AMQP).
12. The data processing system of claim 9 , wherein the passing of the tenant context to the second service of the application further comprises:
setting the tenant context for the second service based on the recovered tenant identity, wherein the key value store connection includes Amazon S3 “Simple Storage Service”.