Ask HN: Best on-disk store for message queue?

Following the interesting discussion [1] around Badger KV store and the different on-disk storage options (Btree, LSM, etc), I was wondering what would be the best approach for a persistent message queue. This comment[2] offers some useful advice for a couple of usecases (write vs read intensive), but as far as I can tell, a message queue has a unique access pattern (heavilty concurrent writes (PUT) and deletes (GET)).

[1] https://news.ycombinator.com/item?id=14335931

[2] https://news.ycombinator.com/item?id=14337588