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

Establish requirements for a single underlying storage engine #9750

Closed
2 of 3 tasks
Tracked by #9749
thanethomson opened this issue Nov 22, 2022 · 0 comments
Closed
2 of 3 tasks
Tracked by #9749

Establish requirements for a single underlying storage engine #9750

thanethomson opened this issue Nov 22, 2022 · 0 comments
Labels
C:storage Component: Storage stale for use by stalebot T:tracking Tracking issue for other issues

Comments

@thanethomson
Copy link
Contributor

thanethomson commented Nov 22, 2022

In order to simplify Tendermint's storage mechanism, we need to first establish what typical usage patterns look like. Given that we intend on offloading event indexing, this effort should focus on understanding and gathering data on what the storage workloads look like for specific use cases. This is a tracking issue for everything that needs to be completed in order to end up with a set of requirements for a database that will serve as Tendermint's storage mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:storage Component: Storage stale for use by stalebot T:tracking Tracking issue for other issues
Projects
Status: Done/Merged
Development

No branches or pull requests

2 participants