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

Why was HaloDB not considered? #26

Open
arjunsk opened this issue Sep 2, 2022 · 2 comments
Open

Why was HaloDB not considered? #26

arjunsk opened this issue Sep 2, 2022 · 2 comments

Comments

@arjunsk
Copy link

arjunsk commented Sep 2, 2022

I had a quick question regarding the purpose of StormDB:

  • Was HaloDB not sufficient for your use case?
  • How does StormDB compare against HaloDB? I think, both StormDB & HaloDB have similar purposes ie both seem to be log-structured KV-store written in Java for fast point lookup and iteration.

PS: The codebase is clean and simple. Great job!

@judepereira
Copy link
Member

Hey @arjunsk, HaloDB was considered in the internal tests, and due to poor performance, we removed it out of the comparison.

Also, StormDB isn't a log structured KV store.

@arjunsk
Copy link
Author

arjunsk commented Sep 5, 2022

Hey @judepereira,

Thanks for the response.

I am having some follow-up questions,

  • What was the project use case for building StormDB? (I read the motivation statement which talked about sequential reads, but where was the sequential read important?)
  • Is it used inside CleverTap mobile SDK? Or at the server side? (I couldn't find any CleaverTap OSS project which used StormDB)

Looking forward to your reply!

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