Skip to content

feat: fallback cache and lock driver #546

Closed
@ibrunotome

Description

@ibrunotome

Is your feature request related to a problem? Please describe.

Recently, I got almost 100 concurrent requests to debit balance from one wallet via api, and I got a redis exception "could not acquire lock"

Describe the solution you'd like

Read data directly from database when could not acquire lock (and update the state in redis in the next request)

Describe alternatives you've considered

Tried other cache drivers, but the only centralized is redis, array driver for example would give two different results if you access balance in a http container vs a container for queues for example.

P.S: I would put a warning about that non centralized cache drivers in the docs.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestquestionFurther information is requested

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions