Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use redis for backend #163

Closed
rmad17 opened this issue Feb 21, 2017 · 1 comment
Closed

Use redis for backend #163

rmad17 opened this issue Feb 21, 2017 · 1 comment

Comments

@rmad17
Copy link

rmad17 commented Feb 21, 2017

Can't we store the data in redis. I dont want hits on my db from silk code. Is that possible?

@avelis
Copy link
Collaborator

avelis commented Feb 21, 2017

There is no direct support to use Redis as a backend. Solutions to use Redis could be using CacheOps to cache access to a Redis instance but still uses the DB.

Another solution could be to listen to pre_save signals of the model to also store the data to a redis instance and block the actual save. However, I couldn't guarantee it would work.

You could also try the multi-db configuration With a custom router and store the Silk data in a db not connected to your main datastore.

Many options that don't involve directly changing this library which I hope can help.

@avelis avelis closed this as completed Apr 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants