Oak
A Scalable Concurrent Key-Value Map for Big Data Analytics (by yahoo)
MapDB
MapDB provides concurrent Maps, Sets and Queues backed by disk storage or off-heap-memory. It is a fast and easy to use embedded Java database engine. (by jankotek)
Oak | MapDB | |
---|---|---|
2 | 5 | |
266 | 4,834 | |
-0.4% | - | |
0.0 | 0.0 | |
4 months ago | 4 months ago | |
Java | Java | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Oak
Posts with mentions or reviews of Oak.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-11.
-
JEP draft: 64 bit object headers
Another to add to your collection, https://github.com/yahoo/Oak
-
Solution for hash-map with >100M values
Consider using an database (e.g. H2 embedded, redis) with an on-heap cache (e.g. Caffeine). Since you say it is a Zipfian distribution, the cache should absorb most of the requests. For an off-heap hashtable, you might try Oak as it is likely a faster implementation.
MapDB
Posts with mentions or reviews of MapDB.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-27.
-
GC, hands off my data!
I decided to start with an overview of what open-source options are currently available. When it comes to the implementation of the on-heap cache mechanism, the options are numerous – there is well known: guava, ehcache, caffeine and many other solutions. However, when I began researching cache mechanisms offering the possibility of storing data outside GC control, I found out that there are very few solutions left. Out of the popular ones, only Terracotta is supported. It seems that this is a very niche solution and we do not have many options to choose from. In terms of less-known projects, I came across Chronicle-Map, MapDB and OHC. I chose the last one because it was created as part of the Cassandra project, which I had some experience with and was curious about how this component worked:
-
Permazen: Language-natural persistence to KV stores
So, it's an object database, like Zope's ZODB on Python?
I like the idea, but I'd like to learn about use cases for it.
Otherwise, in Java, MapDB is about as far as I'd be willing to go: https://github.com/jankotek/mapdb/
-
what is the best persistent collection library?
Anyway, without further ado, I found MapDB (https://github.com/jankotek/mapdb) which does exactly that. Of course, they also provide their own Java collection implementations as well, so I suspect using it with Vavr would be a poor idea, but it is very cool in its own right anyway. Of course, there is also Apache Derby and HSQLDB, and those great options with a long history as well. I haven't played with these in a while though, so I might give them a try again soon for some personal stuff.
-
Ask HN: What are the best key-value self-hosted storage engines?
In Java I like
https://mapdb.org/
It is more feature rich than you want but in Python I'd probably just use sqlite3 since it is in the standard library.
-
Solution for hash-map with >100M values
I have had good results with mapdb