Hi friends! We are planning a rewrite of one of ou...

# getting-started

[Paulo Cereda]

Hi friends! We are planning a rewrite of one of our tools (already in Kotlin) and we need to pick up a (embedded) database. The tool makes heavy use of coroutines and would case lots of concurrent writes to the database. My initial choices would be H2 (I read about DB corruption, which worries me), SQLite (but it seems to be single threaded), and Kotlin's mapdb. Any suggestions are welcome! Thanks!

[AndreyVanDenHaag]

testcontainers? I do not use any other solution for years...

[Paulo Cereda]

@AndreyVanDenHaag I will check it out, thanks! gratitude thank you

[Adam S]

I've been trying to find a good embedded db for caching data in a Kotlin JVM application. I didn't find a great option, but two of the best candidates were

• LMDB (using https://github.com/lmdbjava/lmdbjava)
• RocksDB (using https://github.com/facebook/rocksdb/wiki/rocksjava-basics)
I decided to try RocksDB first, and my attempt is still WIP. It's quite tricky, because there are lots of options, but I like that it supports (or at least claims to support, I've yet to use it in anger) key-based locking (which can either be pessimistic or optimistic), which I think will be useful for highly concurrent access.

[Paulo Cereda]

@Adam S Thanks, Adam! RocksDB looks amazing! gratitude thank you