Riak's company blog, from the makers of the Riak distributed database, covers Bitcask, vector clocks, and why to avoid microservices.
HN commenters praise the 'Microservices – Please, Don't' post as a succinct counter to microservice claims, and value the Bitcask paper and vector clock articles.
I don't know of any rule of English grammar that would lead to this interpretation. If you do, you should immediately write to the maintainers of these websites:
https://redis.com/nosql/key-value-databases/
https://www.mongodb.com/databases/key-value-database
https://aws.amazon.com/nosql/key-value/
https://etcd.io/docs/v3.4/learning/why/
https://riak.com/products/riak-kv/
https://rocksdb.org/
https://github.com/google/leveldb
http://www.memcached.org/
Not papers or books, but I'd recommend you look at the blog articles and such that Basho published about their design of Riak. In particular, they wrote a great article explaining vector clocks as opposed to other synchronizing mechanisms, and they wrote several good articles on CRDTs.
https://riak.com/category/technical/ - Riak blog
https://www.allthingsdistributed.com/files/amazon-dynamo-sosp2007.pdf - Dynamo paper that Riak was in part based on
Microservices to reduce complexity and coupling is a fallacy. https://riak.com/posts/technical/microservices-please-dont/ is a great and succinct counter to all the advantages that microservices claim to have. In summary:
> You don’t need to introduce a network boundary as an excuse to write better code
> Distributed Transactions are never easy
> A bunch of engineers working in isolated codebases leads to ‘Not my problem’ syndrome
It's realistically for the handful (dozens at most?) of very large Riak implementations where it would be enormously expensive to rewrite the application running on top of it.
For example, the UK NHS Spine messaging system which has been building on Riak for 10 years
https://riak.com/posts/press/nhs-launches-upgraded-it-backbone-spine-powered-by-riak/index.html?p=5044.html
I hadn't heard about bitcask before. Its design looks like a great alternative to LSM trees or B+trees like lmdb. Are there any good benchmarks comparing the approaches?
The introductory whitepaper on bitcask's design is here: https://riak.com/assets/bitcask-intro.pdf
Interesting website design: https://riak.com - reminds me of CSS Zen Garden. (Not that it says anything about how it performs etc.)