Django, Databases, and Decorators: Routing Requests to Different Databases

Connecting and using multiple databases in Django

As a growing company with a growing customer base, we’re always thinking about ways to boost the performance of our app (but who isn’t?). We’ve got some long-running queries that occasionally result in page timeouts, and if not, some general slowness for the user. These are things to be avoided. This week, we connected our follower database to the app to pull some of these read-only queries off of the main database to decrease the load.

Initial setup of an additional (already existing) database is fairly basic, and can be done by following the docs. We have something like this in our settings:

All database queries, both reads and writes, will run off of ‘default’ unless you specify otherwise. You can make a query off of the ‘read-only’ database like so:

Seems great. And is great, if your scope is limited. But I don’t want .using('read-only’) calls sprinkled all throughout my app, and I don’t want to remember to write them. We wanted to be able to specify a different database than the default for an entire view method (controller action, for the Rails folks out there), that would apply to every call within it. Decorators to the rescue!

What are decorators?

Coming from a Rails background, the closest equivalent I can come up with is a before_action, though Django’s decorators are actually a little more versatile in that. Basically, they are functions that take another function as an argument, and execute their own code around it. Whereas before_actions in Rails happen, definitionally, before the action (function) is called, decorators wrap around a function and can execute code both before and after. Here’s a common use case:

You’d call this like so:

Writing a custom decorator

A lot of what comes next was inspired by this blog, with some tweaks to fit our use case. You can read more about threading here.

Where you put your decorator depends on where you think you’ll use it — you know best! We may use ours project-wide, so they’re in an app called ‘common’ we have for just that purpose, in a file called Class based decorators aren’t particularly common, but it proves useful for reasons we’ll come back to.

This is what I mean by being able to wrap your code, not just execute something before it, using the __enter__ and __exit__ functions.

You then need a router. More info on routers can be found back in the docs, but basically, they tell the code which database to execute a request on. Our writes will always go to default, while our reads will come from the ‘read-only’ database, if we use the decorator from above:

Back in, don’t forget to add your new router, keeping in mind that they’re run through sequentially, and stop once a match has been found — order matters.

Using the decorator

The benefit of the class based decorator is that it can be used as a decorator:

But it can also be used for a block, if you only want queries in part of a view to be read off the read-only database:

Senior Software Engineer |

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store