Django-Balancer
A set of tools for using Django’s multi-db feature to balance database requests between multiple replicated databases. It currently provides some basic routers for using weighted random selection or round robin selection with a pool of databases, following a master/slave layout where the slaves are read-only copies of master, and pinning reads to master for a user after that user completes a write.
Since everything is implemented using base classes and mixins, this also serves as a construction kit for creating your own more complex routers. Feel free to contribute routers, and I’ll be happy to incorporate them into the project.
Install
Install django-balancer via pip
$ pip install django-balancer
or, with easy_install
$ easy_install django-balancer
But, hey… that’s up to you.
Documentation
Metadata
Release files for django-balancer 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-balancer-0.5.tar.gz | 4.6 kB | Without provenance | Details |
Release files / django-balancer-0.5.tar.gz
| Download URL | django-balancer-0.5.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0583b9897a68b739019f10cffba7fc507578407315ad4e92656e9d77054471d5
|
|
BLAKE2b-256 checksum How to use checksums |
3cf404fbacd5853a43e5d2fed8a64ba00e1687d0de61be002ace2ad73936dd31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-balancer 0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.