Indexing Semantic Versions in Rocksdb

Re:Indexing Semantic Versions in Rocksdb by morelisp on Friday January 05, 2024 @03:19PM (#38884302)

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.

[ Parent | on HN ]

Re:Indexing Semantic Versions in Rocksdb by curtisblaine on Saturday January 06, 2024 @04:50AM (#38890029)

They 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.

[ Parent | on HN ]

Re:Indexing Semantic Versions in Rocksdb by morelisp on Saturday January 06, 2024 @05:50PM (#38896368)

RocksDB 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.

[ Parent | on HN ]

Re:Indexing Semantic Versions in Rocksdb by curtisblaine on Sunday January 07, 2024 @05:49AM (#38900132)

How 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)

[ Parent | on HN ]

Re:Indexing Semantic Versions in Rocksdb by morelisp on Sunday January 07, 2024 @06:11AM (#38900249)

Given the size of any dataset of the type being discussed here, you dump the whole thing to disk on every change.

[ Parent | on HN ]