I am considering a Django stack for a site with high-frequency read (GET) events and low-frequency write (POST) events.
Suppose there are a large number of read-only instances which are all serving GET events and caching various views. There are a smaller number of non-cacheing writeable instances which handle POST events. These instances are all independent and might be running on separate machines, although they access the same central database.
Now suppose there is a POST event which invalidates, say, a user's e-mail address. Then various views across the various read-only instances need to invalidate their caches.
Is there a standard way to implement this pattern within the Django framework, or do I need to do this myself?
(Or there a much better totally different way to do this?)