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

Fully Realize Multi-Datastore #66

Open
bonedaddy opened this issue Apr 10, 2020 · 0 comments
Open

Fully Realize Multi-Datastore #66

bonedaddy opened this issue Apr 10, 2020 · 0 comments
Labels
pending-development details a development task that is pending and will make it into TemporalX

Comments

@bonedaddy
Copy link
Collaborator

Currently we optionally leverage multi-datastore for four different subsystems:

  • Peerstore (in-memory by default)
  • Keystore (in-memory by default)
  • Reference counter store
  • DHT + Provider/Reprovider queue + main storage

To fully realize multi-datastore we need to place DHT + Provider queue in separate datastores, however there are certain situations in which we leverage multiple queues (provider+reprovider, queue based reference counter), and it might be worth considering an umbrella "queue" datastore.
@bonedaddy bonedaddy added the pending-development details a development task that is pending and will make it into TemporalX label Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending-development details a development task that is pending and will make it into TemporalX
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bonedaddy