# django-multitenant <br>[](https://github.com/citusdata/django-multitenant/actions/workflows/django-multitenant-tests.yml) [](https://django-multitenant.readthedocs.io/en/latest/?badge=latest) [](https://codecov.io/gh/citusdata/django-multitenant) [](https://badge.fury.io/py/django-multitenant)
Python/Django support for distributed multi-tenant databases like Postgres+Citus
Enables easy scale-out by adding the tenant context to your queries, enabling the database (e.g. Citus) to efficiently route queries to the right database node.
There are architecures for building multi-tenant databases viz. **Create one database per tenant**, **Create one schema per tenant** and **Have all tenants share the same table(s)**. This library is based on the 3rd design i.e **Have all tenants share the same table(s)**, it assumes that all the tenant relates models/tables have a tenant_id column for representing a tenant.
The following link talks more about the trade-offs on when and how to choose the right architecture for your multi-tenat database:
https://www.citusdata.com/blog/2016/10/03/designing-your-saas-database-for-high-scalability/
**Other useful links on multi-tenancy**:
1. https://www.citusdata.com/blog/2017/03/09/multi-tenant-sharding-tutorial/
1. https://www.citusdata.com/blog/2017/06/02/scaling-complex-sql-transactions/
## Installation:
1. `pip install --no-cache-dir django_multitenant`
## Supported Django versions/Pre-requisites.
| Python | Django |Citus |
| ----------------------| --------------|---------------|
| 3.7 | 3.2 | 10 11 |
| 3.8 3.9 3.10 3.11 | 4.0 | 10 11 |
| 3.8 3.9 3.10 3.11 | 4.1 | 11 |
## Usage:
In order to use this library you can either use Mixins or have your models inherit from our custom model class.
### Changes in Models:
1. In whichever files you want to use the library import it:
```python
from django_multitenant.fields import *
from django_multitenant.models import *
```
2. All models should inherit the TenantModel class.
`Ex: class Product(TenantModel):`
3. Define a static variable named tenant_id and specify the tenant column using this variable.You can define tenant_id in three ways. Any of them is acceptavle
* Using TenantMeta.tenant_field_name variable
* Using TenantMeta.tenant_id variable
* Using tenant_id field
<br>
> **Warning**
> Using tenant_id field directly in the class is not suggested since it may cause collision if class has a field named with 'tenant'
<br>
4. All foreign keys to TenantModel subclasses should use TenantForeignKey in place of
models.ForeignKey
5. A sample model implementing the above 2 steps:
```python
class Store(TenantModel):
name = models.CharField(max_length=50)
address = models.CharField(max_length=255)
email = models.CharField(max_length=50)
class TenantMeta:
tenant_field_name = "id"
class Product(TenantModel):
store = models.ForeignKey(Store)
name = models.CharField(max_length=255)
description = models.TextField()
class Meta:
unique_together = ["id", "store"]
class TenantMeta:
tenant_field_name = "store_id"
class Purchase(TenantModel):
store = models.ForeignKey(Store)
product_purchased = TenantForeignKey(Product)
class TenantMeta:
tenant_field_name = "store_id"
```
### Changes in Models using mixins:
1. In whichever files you want to use the library import it by just saying
```python
from django_multitenant.mixins import *
```
1. All models should use the `TenantModelMixin` and the django `models.Model` or your customer Model class
`Ex: class Product(TenantModelMixin, models.Model):`
1. Define a static variable named tenant_id and specify the tenant column using this variable.
`Ex: tenant_id='store_id'`
1. All foreign keys to TenantModel subclasses should use TenantForeignKey in place of
models.ForeignKey
1. Referenced table in TenenatForeignKey should include a unique key including tenant_id and primary key
```
Ex:
class Meta:
unique_together = ["id", "store"]
```
1. A sample model implementing the above 3 steps:
```python
class ProductManager(TenantManagerMixin, models.Manager):
pass
class Product(TenantModelMixin, models.Model):
store = models.ForeignKey(Store)
tenant_id='store_id'
name = models.CharField(max_length=255)
description = models.TextField()
objects = ProductManager()
class Meta:
unique_together = ["id", "store"]
class PurchaseManager(TenantManagerMixin, models.Manager):
pass
class Purchase(TenantModelMixin, models.Model):
store = models.ForeignKey(Store)
tenant_id='store_id'
product_purchased = TenantForeignKey(Product)
objects = PurchaseManager()
```
### Automating composite foreign keys at db layer:
1. Creating foreign keys between tenant related models using TenantForeignKey would automate adding tenant_id to reference queries (ex. product.purchases) and join queries (ex. product__name). If you want to ensure to create composite foreign keys (with tenant_id) at the db layer, you should change the database ENGINE in the settings.py to `django_multitenant.backends.postgresql`.
```python
'default': {
'ENGINE': 'django_multitenant.backends.postgresql',
......
......
......
}
```
### Where to Set the Tenant?
1. Write authentication logic using a middleware which also sets/unsets a tenant for each session/request. This way developers need not worry about setting a tenant on a per view basis. Just set it while authentication and the library would ensure the rest (adding tenant_id filters to the queries). A sample implementation of the above is as follows:
```python
from django_multitenant.utils import set_current_tenant
class MultitenantMiddleware:
def __init__(self, get_response):
self.get_response = get_response
def __call__(self, request):
if request.user and not request.user.is_anonymous:
set_current_tenant(request.user.employee.company)
return self.get_response(request)
```
In your settings, you will need to update the `MIDDLEWARE` setting to include the one you created.
```python
MIDDLEWARE = [
# ...
# existing items
# ...
'appname.middleware.MultitenantMiddleware'
]
```
2. Set the tenant using set_current_tenant(t) api in all the views which you want to be scoped based on tenant. This would scope all the django API calls automatically(without specifying explicit filters) to a single tenant. If the current_tenant is not set, then the default/native API without tenant scoping is used.
```python
def application_function:
# current_tenant can be stored as a SESSION variable when a user logs in.
# This should be done by the app
t = current_tenant
#set the tenant
set_current_tenant(t);
#Django ORM API calls;
#Command 1;
#Command 2;
#Command 3;
#Command 4;
#Command 5;
```
## Supported APIs:
1. Most of the APIs under Model.objects.*.
1. Model.save() injects tenant_id for tenant inherited models.
```python
s=Store.objects.all()[0]
set_current_tenant(s)
#All the below API calls would add suitable tenant filters.
#Simple get_queryset()
Product.objects.get_queryset()
#Simple join
Purchase.objects.filter(id=1).filter(store__name='The Awesome Store').filter(product__description='All products are awesome')
#Update
Purchase.objects.filter(id=1).update(id=1)
#Save
p=Product(8,1,'Awesome Shoe','These shoes are awesome')
p.save()
#Simple aggregates
Product.objects.count()
Product.objects.filter(store__name='The Awesome Store').count()
#Subqueries
Product.objects.filter(name='Awesome Shoe');
Purchase.objects.filter(product__in=p);
```
## Credits
This library uses similar logic of setting/getting tenant object as in [django-simple-multitenant](https://github.com/pombredanne/django-simple-multitenant). We thank the authors for their efforts.
## License
Copyright (C) 2018, Citus Data
Licensed under the MIT license, see LICENSE file for details.
Raw data
{
"_id": null,
"home_page": "https://github.com/citusdata/django-multitenant",
"name": "gindix-multitenant",
"maintainer": "",
"docs_url": null,
"requires_python": "",
"maintainer_email": "",
"keywords": "citus django multi tenantdjango postgres multi-tenant",
"author": "Louise Grandjonc",
"author_email": "louise.grandjonc@microsoft.com",
"download_url": "https://files.pythonhosted.org/packages/14/9d/267af4f1b83b8572e1804128a8ec43b39a07a004734f98eb78bf4069823b/gindix-multitenant-3.1.1.tar.gz",
"platform": null,
"description": "# django-multitenant <br>[](https://github.com/citusdata/django-multitenant/actions/workflows/django-multitenant-tests.yml) [](https://django-multitenant.readthedocs.io/en/latest/?badge=latest) [](https://codecov.io/gh/citusdata/django-multitenant) [](https://badge.fury.io/py/django-multitenant)\n\nPython/Django support for distributed multi-tenant databases like Postgres+Citus\n\nEnables easy scale-out by adding the tenant context to your queries, enabling the database (e.g. Citus) to efficiently route queries to the right database node.\n\nThere are architecures for building multi-tenant databases viz. **Create one database per tenant**, **Create one schema per tenant** and **Have all tenants share the same table(s)**. This library is based on the 3rd design i.e **Have all tenants share the same table(s)**, it assumes that all the tenant relates models/tables have a tenant_id column for representing a tenant.\n\nThe following link talks more about the trade-offs on when and how to choose the right architecture for your multi-tenat database:\n\nhttps://www.citusdata.com/blog/2016/10/03/designing-your-saas-database-for-high-scalability/\n\n**Other useful links on multi-tenancy**:\n1. https://www.citusdata.com/blog/2017/03/09/multi-tenant-sharding-tutorial/\n1. https://www.citusdata.com/blog/2017/06/02/scaling-complex-sql-transactions/\n\n\n## Installation:\n1. `pip install --no-cache-dir django_multitenant`\n\n## Supported Django versions/Pre-requisites.\n\n| Python | Django |Citus |\n| ----------------------| --------------|---------------|\n| 3.7 | 3.2 | 10 11 |\n| 3.8 3.9 3.10 3.11 | 4.0 | 10 11 |\n| 3.8 3.9 3.10 3.11 | 4.1 | 11 |\n\n\n\n## Usage:\n\nIn order to use this library you can either use Mixins or have your models inherit from our custom model class.\n\n\n### Changes in Models:\n1. In whichever files you want to use the library import it:\n ```python\n from django_multitenant.fields import *\n from django_multitenant.models import *\n ```\n2. All models should inherit the TenantModel class.\n `Ex: class Product(TenantModel):`\n3. Define a static variable named tenant_id and specify the tenant column using this variable.You can define tenant_id in three ways. Any of them is acceptavle \n * Using TenantMeta.tenant_field_name variable\n * Using TenantMeta.tenant_id variable\n * Using tenant_id field\n <br>\n\n\n > **Warning**\n > Using tenant_id field directly in the class is not suggested since it may cause collision if class has a field named with 'tenant'\n <br>\n\n4. All foreign keys to TenantModel subclasses should use TenantForeignKey in place of\n models.ForeignKey\n5. A sample model implementing the above 2 steps:\n ```python\n class Store(TenantModel):\n name = models.CharField(max_length=50)\n address = models.CharField(max_length=255)\n email = models.CharField(max_length=50)\n class TenantMeta:\n tenant_field_name = \"id\"\n \n class Product(TenantModel):\n store = models.ForeignKey(Store)\n name = models.CharField(max_length=255)\n description = models.TextField()\n class Meta:\n unique_together = [\"id\", \"store\"]\n class TenantMeta:\n tenant_field_name = \"store_id\"\n class Purchase(TenantModel):\n store = models.ForeignKey(Store)\n product_purchased = TenantForeignKey(Product)\n class TenantMeta:\n tenant_field_name = \"store_id\"\n ```\n\n\n### Changes in Models using mixins:\n1. In whichever files you want to use the library import it by just saying \n ```python\n from django_multitenant.mixins import *\n ```\n1. All models should use the `TenantModelMixin` and the django `models.Model` or your customer Model class\n `Ex: class Product(TenantModelMixin, models.Model):`\n1. Define a static variable named tenant_id and specify the tenant column using this variable.\n `Ex: tenant_id='store_id'`\n1. All foreign keys to TenantModel subclasses should use TenantForeignKey in place of\n models.ForeignKey\n1. Referenced table in TenenatForeignKey should include a unique key including tenant_id and primary key\n ```\n Ex: \n class Meta:\n unique_together = [\"id\", \"store\"]\n ```\n1. A sample model implementing the above 3 steps:\n ```python\n\n class ProductManager(TenantManagerMixin, models.Manager):\n pass\n \n class Product(TenantModelMixin, models.Model):\n store = models.ForeignKey(Store)\n tenant_id='store_id'\n name = models.CharField(max_length=255)\n description = models.TextField()\n \n objects = ProductManager()\n \n class Meta:\n unique_together = [\"id\", \"store\"]\n \n class PurchaseManager(TenantManagerMixin, models.Manager):\n pass\n \n class Purchase(TenantModelMixin, models.Model):\n store = models.ForeignKey(Store)\n tenant_id='store_id'\n product_purchased = TenantForeignKey(Product)\n \n objects = PurchaseManager()\n ```\n\n\n\n### Automating composite foreign keys at db layer:\n1. Creating foreign keys between tenant related models using TenantForeignKey would automate adding tenant_id to reference queries (ex. product.purchases) and join queries (ex. product__name). If you want to ensure to create composite foreign keys (with tenant_id) at the db layer, you should change the database ENGINE in the settings.py to `django_multitenant.backends.postgresql`.\n ```python\n 'default': {\n 'ENGINE': 'django_multitenant.backends.postgresql',\n ......\n ......\n ......\n }\n ```\n### Where to Set the Tenant?\n1. Write authentication logic using a middleware which also sets/unsets a tenant for each session/request. This way developers need not worry about setting a tenant on a per view basis. Just set it while authentication and the library would ensure the rest (adding tenant_id filters to the queries). A sample implementation of the above is as follows:\n ```python\n from django_multitenant.utils import set_current_tenant\n \n class MultitenantMiddleware:\n def __init__(self, get_response):\n self.get_response = get_response\n\n def __call__(self, request):\n if request.user and not request.user.is_anonymous:\n set_current_tenant(request.user.employee.company)\n return self.get_response(request)\n ```\n \n In your settings, you will need to update the `MIDDLEWARE` setting to include the one you created.\n ```python\n MIDDLEWARE = [\n # ...\n # existing items\n # ...\n 'appname.middleware.MultitenantMiddleware'\n ]\n ```\n2. Set the tenant using set_current_tenant(t) api in all the views which you want to be scoped based on tenant. This would scope all the django API calls automatically(without specifying explicit filters) to a single tenant. If the current_tenant is not set, then the default/native API without tenant scoping is used.\n ```python\n def application_function:\n # current_tenant can be stored as a SESSION variable when a user logs in.\n # This should be done by the app\n t = current_tenant\n #set the tenant\n set_current_tenant(t);\n #Django ORM API calls;\n #Command 1;\n #Command 2;\n #Command 3;\n #Command 4;\n #Command 5;\n ```\n\n## Supported APIs:\n1. Most of the APIs under Model.objects.*.\n1. Model.save() injects tenant_id for tenant inherited models.\n ```python\n s=Store.objects.all()[0]\n set_current_tenant(s)\n \n #All the below API calls would add suitable tenant filters.\n #Simple get_queryset()\n Product.objects.get_queryset()\n \n #Simple join\n Purchase.objects.filter(id=1).filter(store__name='The Awesome Store').filter(product__description='All products are awesome')\n \n #Update\n Purchase.objects.filter(id=1).update(id=1)\n \n #Save\n p=Product(8,1,'Awesome Shoe','These shoes are awesome')\n p.save()\n \n #Simple aggregates\n Product.objects.count()\n Product.objects.filter(store__name='The Awesome Store').count()\n \n #Subqueries\n Product.objects.filter(name='Awesome Shoe');\n Purchase.objects.filter(product__in=p);\n\n ```\n\n## Credits\n\nThis library uses similar logic of setting/getting tenant object as in [django-simple-multitenant](https://github.com/pombredanne/django-simple-multitenant). We thank the authors for their efforts.\n\n## License\n\nCopyright (C) 2018, Citus Data\nLicensed under the MIT license, see LICENSE file for details.\n",
"bugtrack_url": null,
"license": "",
"summary": "Django Library to Implement Multi-tenant databases",
"version": "3.1.1",
"split_keywords": [
"citus",
"django",
"multi",
"tenantdjango",
"postgres",
"multi-tenant"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "149d267af4f1b83b8572e1804128a8ec43b39a07a004734f98eb78bf4069823b",
"md5": "f51fcf5ddabcc97ecaa1f4f868e12b90",
"sha256": "2a3bbb8f3b95a2eabd44b604a13a1c8da7fb253c37f1dde5abed2d91ee8a68de"
},
"downloads": -1,
"filename": "gindix-multitenant-3.1.1.tar.gz",
"has_sig": false,
"md5_digest": "f51fcf5ddabcc97ecaa1f4f868e12b90",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 18177,
"upload_time": "2023-03-15T16:25:29",
"upload_time_iso_8601": "2023-03-15T16:25:29.504624Z",
"url": "https://files.pythonhosted.org/packages/14/9d/267af4f1b83b8572e1804128a8ec43b39a07a004734f98eb78bf4069823b/gindix-multitenant-3.1.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-03-15 16:25:29",
"github": true,
"gitlab": false,
"bitbucket": false,
"github_user": "citusdata",
"github_project": "django-multitenant",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "gindix-multitenant"
}
JSON
