[Leon]

You are correct and I came here to say the same. Additionally I've seen issues working with etcd in that it is a pain to manage, with situations coming about of split cluster issues where the data becomes corrupted and needs to be manually merged together. That is a bad situation to be in, and usually it is better to develop for failure, especially in cloud environments. You can get split-brain problems on any clustered agreement replication, etcd is not a special case.

[iwalz]

These failures are the worst case for any technology like that and will always cause a bit pain in production - but since the etcd guys a very open to how they behave in case of failures and how they do quality testing of etcd, I started to trust etcd: https://coreos.com/blog/new-functional-testing-in-etcd/

I have read a blog post about continous testing of consul at high scale too (can't find the link for now), but I can't remember to got this much insights.

[ideal0227]

There is a dashboard for publishing the testing result at realtime at http://dash.etcd.io/dashboard/db/functional-tests. The result is not super clear right now, we are improving it.