RocksDB VS Amium

RocksDB mentions (11)

• How to choose the right type of database

  RocksDB: A high-performance embedded database optimized for multi-core CPUs and fast storage like SSDs. Its use of a log-structured merge-tree (LSM tree) makes it suitable for applications requiring high throughput and efficient storage, such as streaming data processing. - Source: dev.to / 2 months ago

• Fast persistent recoverable log and key-value store

  [RocksDB](https://rocksdb.org/) isn’t a distributed storage system, fwiw. It’s an embedded KV engine similar to LevelDB, LMDB, or really sqlite (though that’s full SQL, not just KV). - Source: Hacker News / 2 months ago

• The Hallucinated Rows Incident

  To output the top 3 rocks, our engine has to first store all the rocks in some sorted way. To do this, we of course picked RocksDB, an embedded lexicographically sorted key-value store, which acts as the sorting operation's persistent state. In our RocksDB state, the diffs are keyed by the value of weight, and since RocksDB is sorted, our stored diffs are automatically sorted by their weight. - Source: dev.to / 6 months ago

• In-memory vs. disk-based databases: Why do you need a larger than memory architecture?

  Memgraph uses RocksDB as a key-value store for extending the capabilities of the in-memory database. Not to go into too many details about RocksDB, but let’s just briefly mention that it is based on a data structure called Log-Structured Merge-Tree (LSMT) (instead of B-Trees, typically the default option in databases), which are saved on disk and because of the design come with a much smaller write amplification... - Source: dev.to / 8 months ago

• Event streaming in .Net with Kafka

  Streamiz wrap a consumer, a producer, and execute the topology for each record consumed in the source topic. You can easily create stateless and stateful application. By default, each state store is a RocksDb state store persisted on disk. - Source: dev.to / over 1 year ago

Amium mentions (0)