bdarfler
https://www.slideshare.net/AmazonWebServices/cmp402-amazon-e...
Testing AWS Scala Microservices
https://www.usenix.org/conference/nsdi15/technical-sessions/...
Using Enumerations to Make a Faster Activity Feed in Rails
11 Best Practices for Low Latency Systems
Mathematical Purity in Distributed Systems: CRDTs Without Fear
NoSQL Database Comparison
I got tired of remembering all the features of the various NoSQL dbs. Here’s a site for all to use. Please help contribute.
Web Scale Analytics Reading List
A Sequential I/O Reading List
P.S. If your stack is KV then you should use a KV store.
These days auto-sharding works and works well. There is a learning curve to optimize it (i.e. picking a good shard key, analogous to picking a good _id field) but that is to be expected.
Replica sets work exactly as advertised in my experience. Automatic fail over and no need to wake up at 3am is a huge win.
Finally single server durability directly addresses durability concerns that many have.
The first two points are the reason why my company and so many others are switching even if that means needing to understand how to pick good ids/shard keys and having to shorten our field names by hand. I can see why, if they were not available at the time, MongoDB might not be a good choice but the fact of the matter is that they are available today.