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

[rfc] move caches into redis #104

Open
hawkrives opened this issue Dec 15, 2018 · 1 comment
Open

[rfc] move caches into redis #104

hawkrives opened this issue Dec 15, 2018 · 1 comment

Comments

@hawkrives
Copy link
Member

thoughts?

seems like that's kinda … one of redis' specialities.

downsides: added dependency, but Docker/-compose should make that almost painless…

@hawkrives hawkrives changed the title [rfc] move caches into redis? [rfc] move caches into redis Dec 15, 2018
@rye
Copy link
Member

rye commented Dec 15, 2018

I am wholeheartedly in favor of this.

Just expanding on a couple of points.

Pros

  • Caches that persist continuously through ccc, et al. updates.
  • Caches that could be shared between all of our containers.
  • Cache expiration handled natively by redis internally.
  • Redis can handle storing Strings, Hashes, Lists, Sets, Sorted Sets.
  • Depending on client support for it, Redis also supports pipelining.

Cons

  • Potential for added latency (rather than SHM, we'd be shelling out to an "external" service)
  • Added dependency (both in each project that consumes it, and also on the server)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants