Why coredis instead of redis-py and compatibility with Valkey ?

[nsteinmetz]

Hi there,

Considering an alternative to arq, I found your project and diving into details to see if it could replace arq by streaq.

Answer seems yes 🎉

Two questions I have in mind before going further:

• Why use coredis instead of redis-py ?
• Did you evaluate the compatibility of streaq with Valkey ? I'm not clear yet if I keep Redis or switch to Valkey.

Thanks in advance for your answers.

[Graeme22]

Hello! Coredis is used because it's async first and has way better typing. Valkey is supported, I use it myself :)

[nsteinmetz]

thanks for the precisions !

Indeed, redis-py became async ready once aioredis was merged for 4.2 release and it was improved since then.

Was curious as I would have thought that using the official client would have made more sense but that's good arguments :)

[espdev]

@Graeme22

Just thoughts. Right now, either Redis DSN or Sentinel parameters are pass in the Worker constructor.
It would be nice to be able to pass an instance of an already configured Redis client to the Worker, or at least be able to set additional Redis parameters in the Worker.. This would allow us to customize some additional parameters, timeouts, etc.

[Graeme22]

Good idea, will add a redis_kwargs parameter for the next release!

[ferdimsu]

Yeah that would be appreciated!

[Graeme22]

This is availble now :)

[Graeme22]

By the way, I think the library will probably switch back to redis-py if any of the typing-related PRs ever gets merged. I have had a few problems with coredis lately and the performance is slightly worse.

[Graeme22]

If you're able to track it down please open an issue either upstream or here

[jashwant]

@Graeme22 , any plan to switch to redis-py?

[Graeme22]

@Graeme22 , any plan to switch to redis-py?

Definitely not! This conversation is very outdated. A few reasons why:

• streaQ now uses structured concurrency and supports Trio, little chance redis-py ever does that
• redis-py still has awful types
• I've been involved in a lot of work on coredis, reliability is much better and it's actually more performant than redis-py now

Instead consider switching to coredis once version 6 is out (should be within a week or two), I think it's far superior to redis-py in most respects

[jashwant]

I was moving away from celery. And was deciding between taskiq-python and streaq. Streaq looks more packed, but less popular. Similarly redis-py is more popular than coredis.

But your comment gave me confidence that streaq is not going to be abandoned in near future.
Thanks a lot for this great library.

[Graeme22]

I was moving away from celery. And was deciding between taskiq-python and streaq. Streaq looks more packed, but less popular. Similarly redis-py is more popular than coredis.

But your comment gave me confidence that streaq is not going to be abandoned in near future.

Thanks a lot for this great library.

Both streaQ and coredis are actively maintained, if you ever run across anything open an issue. Taskiq is a great choice as well!