[hayst4ck]

> And unless you enjoy telling war stories about how your junior team member ran "flushdb" in production and caused your service traffic to stall, or how your engineering team spent a month tuning the Redis engine before Christmas —you should really think whether this is how you want to spend your time. Engineers should not spend their careers intimately memorizing random quirks of the infrastructure they use. They deserve better. They deserve boring.

I'm not sure this person understands infrastructure. I can't think of very many datastores that weren't boring... until you got 50% more traffic in a week, until a rack that 10% of your capacity is in fails, until someone's code update caused a DDOS resulting in requests going to the machine taking 100ms in stead of 1ms.

So does boring mean it scales trivially and tolerates failure in well defined ways?