MapDB
kotlin-jpa-specification-dsl
Our great sponsors
MapDB | kotlin-jpa-specification-dsl | |
---|---|---|
5 | 1 | |
4,829 | 247 | |
- | 1.2% | |
0.0 | 0.0 | |
3 months ago | over 2 years ago | |
Java | Kotlin | |
Apache License 2.0 | Apache License 2.0 |
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.
MapDB
-
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
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
kotlin-jpa-specification-dsl
-
What is the Specification Pattern
If you are using Kotlin, kotlin-jpa-specification-dsl provides a very convenient way to generate Specifications from KPropertys.
What are some alternatives?
Chronicle Map - Replicate your Key Value Store across your network, with consistency, persistance and performance.
requery - requery - modern SQL based query & persistence for Java / Kotlin / Android
H2 - H2 is an embeddable RDBMS written in Java.
Exposed - Kotlin SQL Framework
JetBrains Xodus - Transactional schema-less embedded database used by JetBrains YouTrack and JetBrains Hub.
Ktorm - A lightweight ORM framework for Kotlin with strong-typed SQL DSL and sequence APIs.
Redisson - Redisson - Easy Redis Java client with features of In-Memory Data Grid. Sync/Async/RxJava/Reactive API. Over 50 Redis based Java objects and services: Set, Multimap, SortedSet, Map, List, Queue, Deque, Semaphore, Lock, AtomicLong, Map Reduce, Bloom filter, Spring Cache, Tomcat, Scheduler, JCache API, Hibernate, RPC, local cache ...
kt-postgresql-async - Kotlin 1.1 async clients for sync protocols: Mysql, Postgres, Thrift, Http
Jedis - Redis Java client
kmongo - [deprecated] KMongo - a Kotlin toolkit for Mongo
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL