You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My personal preference is BoltHold. It's more simple and straightforward, and I've run into less issues with it, but you are correct that it generally performs slower than Badger. However if your goal is performance or you are dealing with large datasets, then my recommendation will always be SQLite.
The entire goal of creating Bolthold was to have something that still had good performance, but was primarily easy to use. It's goal was to compete with writing your application state to text files, not necessarily replacing an entire DBMS.
Hi Tim,
thanks for your answer. I think for my purpose every solution feels adapted, I don't have today a lot of performance constraint. And for a website that manage media and page content for some users (not much), it could do the trick very well.
I'll read your post
Hi,
and thanks to share your work.
Your 2 packages feel really cool,
So which one should I use, it feels that badger is better in terms of performance and maintenance over bolt.
But I also really like boltholdSliceIndex that I didn't find in badgerhold. Why it was not implemented in badgerhold?
Thanks for your help
The text was updated successfully, but these errors were encountered: