RE: Why Isn't HAF Used More?
You are viewing a single comment's thread:
They don't access a local file sequentially.
HIVE nodes already have a DB table (rocks db) in the background for every endpoint ('plugin').
So unless you need very 'custom' API, you don't need HAF.
And then, you can probably custom build one, without the use of HAF.
Which I have build. I call it the HIAF (HIVE idiot app framework) and it has 200 lines of code and was done in a weekend. It doesn't have a fork manager, but I can't think of an app that would need reversible blocks.
HIAF replay might be slower, but I don't have the ressources to test.
0
0
0.000
Well, I don't know enough about Hive nodes or HAF to debate you on these matters. 😀
EDIT: However, I have a question. If Hive nodes have Rocks DB behind them (and I've heard of it, but didn't know where it was used), why can't I "get" one of my posts from 3 months ago and I have to scroll back through all the history? Why don't front ends offer a search option?
You can (check the 'start' parameter) but you'd have to know the index number.
My guess is it was designed like that for scalability. At the end of the day, every table is just a list in memory and the more keys, the more tables, more memory.
HIVE Engine allows it (noSQL style) and it seems to work ok, too.
That index doesn't help with searches much. But I understand the limitations. Rocks DB uses RAM, not disk on Hive nodes, right? Or it's an option that can be set?
That's the part I don't understand all that well...
It clearly can't use only RAM, as it's in the TerraBytes for a 'full-node'.
You can manipulate where what is stored on OS level, I guess...
I remember using something like RAMdisk... But I just copied that and never understood how the OS deals with this stuff in the background.
Thanks for the feedback!