4 ms·
Using RocksDB here seems fairly insane unless you need to keep (at least) several billion constantly-updating versions sorted. Otherwise you can just use Sorted
by morelisp 3y ago
Using RocksDB here seems fairly insane unless you need to keep (at least) several billion constantly-updating versions sorted. Otherwise you can just use SortedMap and regular Java comparators.
- curtisblaine 3y agoThey might just want cheap disk persistence. I'm not a Java developer, but if SortedMaps are a memory-only data structure, persisting them reliably doesn't look an easy feat.
- morelisp 3y agoRocksDB is disk persistence but it sure ain't (for this scale) cheap. Persisting just about anything in Java is easier than persisting it in Java in RocksDB.
- curtisblaine 3y agoHow would you persist a Sorted Map in Java easily? Serializing and deserializing is OK, but keep in mind that if the program crashes you still need to persist all the data that was saved before the crash (so you can't keep in memory and serialize at exit, or at a time interval)
- morelisp 3y agoGiven the size of any dataset of the type being discussed here, you dump the whole thing to disk on every change.