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.

Sign up for GitHub

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

Jump to bottom

[Feat]: redis backend for dedup cache #2004

Open
elee1766 opened this issue Nov 3, 2023 · 2 comments · May be fixed by #2005
Open

[Feat]: redis backend for dedup cache #2004

elee1766 opened this issue Nov 3, 2023 · 2 comments · May be fixed by #2005
Labels
feature New feature or request no-issue-activity rm-external Roadmap item submitted by non-maintainers work-in-progress

Comments

@elee1766
Copy link
Contributor

elee1766 commented Nov 3, 2023

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

i would like to use something that is not dynamodb as a distributed dedup cache.

Describe the solution you'd like

redis seems like a good candidate for this. there was already a dependency for redis in the package, so i felt it was a good choice.

Describe alternatives you've considered

No response

Additional context

No response
@elee1766 elee1766 added the feature New feature or request label Nov 3, 2023
@elee1766 elee1766 linked a pull request Nov 3, 2023 that will close this issue
Draft
@rchincha rchincha added the rm-external Roadmap item submitted by non-maintainers label Nov 3, 2023
@rchincha
Copy link
Contributor

rchincha commented Nov 3, 2023

@elee1766 is this for a cloud deployment use case?

@elee1766
Copy link
Contributor Author

elee1766 commented Nov 3, 2023 •
edited

yep!

I plan to combine this with the s3 storage

I am also currently working on the ability to use s3 storage with the sync backend.

my use case is to use zot as a proxy to balance between two identical container registries. I would like the cached images to stay existent between runs without configuring persistent storage. currently there's like a long delay on first pull which I would like to avoid.

ideally I am trying to host a distributed zot cluster using a PAAS platform, like heroku, fly, digitalocean app engine, etc. they all support redis but not dynamo since that's aws only

@rchincha rchincha linked a pull request Apr 4, 2024 that will close this issue
feat: redis dedup backend #2005
Draft
rchincha pushed a commit to rchincha/zot that referenced this issue Apr 8, 2024
@elee1766 @rchincha
feat: add redis cache support
a00259c 
project-zot#2005
Fixes project-zot#2004
peusebiu pushed a commit to peusebiu/zot that referenced this issue Apr 30, 2024
@elee1766 @peusebiu
feat: add redis cache support
a702384 
project-zot#2005
Fixes project-zot#2004
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature or request no-issue-activity rm-external Roadmap item submitted by non-maintainers work-in-progress
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: redis dedup backend elee1766/zot
2 participants
@elee1766 @rchincha