Since REDIS is already usable as a cache for Django using 3rd party code, I would rather see a circuit breaker pattern applied to the cache, across all backends. I'm not that active in maintaining Django right now, but a cache may not be fully redundant, and it also can fail. If the cache is truly used as a cache, then it should be possible to try the cache, and if it fails for several tries, then Django could start to bypass it, and then try to re-enable it later.
This is perhaps a bigger effort than a GSOC project - the hard part is doing this across multiple processes and threads. What does it mean if the cache is only available for some fraction of the instances/processes hosting a project? On Thu, Apr 1, 2021 at 8:25 AM Girish Sontakke <[email protected]> wrote: > Hello Carlton, > As suggested by you I made some revisions to my proposal. Still, it is not > a perfect one, I am trying to improve it. Thanks a lot for the help. > > Kind Regards, > Girish > On Thursday, April 1, 2021 at 12:15:53 AM UTC+5:30 [email protected] > wrote: > >> >> >> On 31 Mar 2021, at 11:00, Girish Sontakke <[email protected]> wrote: >> >> Now I have doubt that whether I should remove *Provides Many >> Data-Structures *point from the "Why Redis" section or keep it there?. >> >> >> I don’t think it’s vital either way… but it seems a distraction. That >> Redis has HyperLogLog isn’t something that will matter at all to the cache >> backend. >> >> I’d try to focus on the details of the implementation: Look at the >> backend API, set(), get() &co. Look at the two existing third-party >> backend, and see what they do there. >> >> I’d also think about getting the documentation right — there are a few >> options with installs and connections and … — you don’t have to solve all >> of those in the proposal but showing that you’re aware of them would be >> good. >> >> I hope that helps. >> >> Kind Regards, >> >> Carlton >> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/97c757dd-b09f-49f4-9e3f-0ee4a8e4887cn%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/97c757dd-b09f-49f4-9e3f-0ee4a8e4887cn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFzonYbS8Tphvvdae6fEs7zb_EH30WKJx7r1_bP5BBBWFWqm9A%40mail.gmail.com.
