I’ve been encountering quite a few django Apps mentioning ‘backend’, but don’t exactly know what it is. Searching around google does not give much results regarding django backends in general. Could someone give an explanation?
To be specific, take these examples:
- django.contrib.auth.backends.ModelBackend
- django.contrib.sessions.backends.cache
- “The messages framework can use different backends to store
temporary messages”
Actually I think the first two and the third are a bit different, what I was more unsure about was the first two: backends included in Apps.
django comes with one or more implementations of authentication, caching, etc but the framework anticipates the need for adding your own custom “backend” implementation. They generally provide a simple well-documented interface as well as a setting variable so it is easy to plug in your own custom module.
This term/pattern is also used by common django apps such as django-registration.
If you are into design patterns this blog provides some analysis: http://charlesleifer.com/blog/django-patterns-pluggable-backends/