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

[FEATURE] Distributed Cache strategy #58

Open
imyousuf opened this issue Jan 19, 2021 · 0 comments
Open

[FEATURE] Distributed Cache strategy #58

imyousuf opened this issue Jan 19, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@imyousuf
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
There is a lot of primary key based DB reads in the flow of Message dispatch; similar calls are there for endpoints as well. We
want to avoid repetitive calls to DB for Producer, Channel and Consumer. This should reduce the load of read from DB.

Describe the solution you'd like
We are able to use golang/groupcache along with mailgun/gubernator (it will be used for #53 and has peer auto-discovery implemented).

Describe alternatives you've considered
memcached and redis were obvious alternates; but in process and in-memory will definitely result in in best performance.

Additional context
This is purely a optimization to reduce DB load.

@imyousuf imyousuf added the enhancement New feature or request label Jan 19, 2021
@imyousuf imyousuf added this to the v0.2 milestone Jan 19, 2021
@imyousuf imyousuf added this to Backlog in Broker Board via automation Jan 21, 2021
@imyousuf imyousuf self-assigned this Apr 5, 2021
@imyousuf imyousuf modified the milestones: v0.2, v0.3 Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant