dapr / dapr/components-contrib
Is Redis actually transactional?
- Dominant language
- Go
- Stars
- 602
- Forks
- 580
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Our docs report Redis state store as "Transactional" because it allows to send multiple Update/Delete operations at once and to be executed "together". But does it actually have ACID guarantees?
https://docs.dapr.io/reference/components-reference/supported-state-stores/
https://github.com/go-redis/redis/issues/1602
Contributor guide
Research direction
Review the supported state stores documentation and the linked go-redis issue to determine whether Redis transactions provide ACID guarantees for batched Update/Delete operations. Compare the documented "Transactional" label with the evidence, then update the Redis entry so its transaction semantics are accurately described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100