aiocache icon indicating copy to clipboard operation
aiocache copied to clipboard

Valkey/Redis Windows support

Open sakosha opened this issue 5 months ago • 6 comments

With valkey-glide merged, we lost support for windows clients.

See upstream issue https://github.com/valkey-io/valkey-glide/issues/3780. Leave 😄 emoji on upstream issue to signal your interest.

If you use RedisCache please pin aiocache<=0.12.3 for now.

sakosha avatar Jun 21 '25 10:06 sakosha

If you use RedisCache please pin aiocache<=0.12.3 for now.

ValkeyCache replaces RedisCache, so if you have any version with RedisCache (<1) then it will still be working.

Guess some more users will need to leave feedback in that issue to make it known that Windows support is needed.

Dreamsorcerer avatar Jun 21 '25 11:06 Dreamsorcerer

We are currently working on Windows support, we don't have timelines. We will share once we have ETAs.

asafpamzn avatar Jun 22 '25 20:06 asafpamzn

@Dreamsorcerer @sakosha just a thought: If valkey-glide takes a while to add windows support and you're looking to release v1 prior, a Windows user from the community could pull the Redis implementation from before #975 merged into it's own aiocache-redis-windows third-party repo & package, similar to aiocache-dynamodb. I suppose they'd need to upgrade it a bit to make it 1.0 compatible, but that doesn't look like a crazy amount of work.

jskrzypek avatar Jun 23 '25 16:06 jskrzypek

Why use ValkeyCache instead of RedisCache? What are the benefits? Is it necessary?

pendy99 avatar Aug 24 '25 04:08 pendy99

Given the licensing situation of redis/valkey, we are moving things to valkey (in the short term atleast, these are compatible). The main difference is that ValkeyCache has changed to use the glide client. This client significantly faster (our benchhmark test that verifies that 25% of requests get through started failing on redis last year, valkey achieves 100% of requests everytime) and doesn't cause a race condition on redlock.

Dreamsorcerer avatar Aug 24 '25 10:08 Dreamsorcerer

Given the licensing situation of redis/valkey, we are moving things to valkey (in the short term atleast, these are compatible). The main difference is that ValkeyCache has changed to use the glide client. This client significantly faster (our benchhmark test that verifies that 25% of requests get through started failing on redis last year, valkey achieves 100% of requests everytime) and doesn't cause a race condition on redlock.

good job! when release?

pendy99 avatar Aug 24 '25 15:08 pendy99