>
> The recent survey showed 70% of our users using redis for caching, with
> 20%+ using memcached.


Oh I see you brought data to an opinion fight :)

Okay if those are even within 20% of the truth, it completely makes sense
to add Redis support! +1

On Tue, 18 Aug 2020 at 14:54, Tobias McNulty <[email protected]> wrote:

> On Tue, Aug 18, 2020 at 9:34 AM Carlton Gibson <[email protected]>
> wrote:
>
>> I think we SHOULD bring a redis cache backend into core.
>>
>> The recent survey showed 70% of our users using redis for caching, with
>> 20%+ using memcached.
>>
>> Nick is working on
>> https://github.com/django/django/pull/13310 now.
>>
>> This’ll give us three memcached backends and zero for redis.
>> That doesn’t seem right.
>>
>> The cache backend API is small and redis is stable. I think we can offer
>> that, freeing third party packages some work, to do the more interesting
>> things.
>>
>
> +1, even as someone who does not self-identify as a Redis enthusiast.
>
>
> *Tobias McNulty*Chief Executive Officer
>
> [email protected]
> www.caktusgroup.com
>
> --
> 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/CAMGFDKT%2B_x%3D2Yb-d1SuzcTpzuzhDmT%2Bh1FqpuV_5i2%2BY%3D%2B32OA%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAMGFDKT%2B_x%3D2Yb-d1SuzcTpzuzhDmT%2Bh1FqpuV_5i2%2BY%3D%2B32OA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Adam

-- 
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/CAMyDDM1A_eCMDTSEmE3uLi5TjM-e9NSazkRHWfWwtgD%3DTQEFFQ%40mail.gmail.com.

Reply via email to