I think you touched on a key point a lot of people don&#x27;t consider.  Not all data is the same nor does it have to be treated the same.  Many distributed systems will choke on a piece of data here and there and may not give the appropriate response.  But you need to consider what you&#x27;re working on and if that&#x27;s OK from time to time given the advantages the system you&#x27;re considering offers.<p>What might be considered an appropriate data store for one data set may not be for another.  And the type of information a lot of distributed systems are handling are far from bank accounts, for example.<p>And if you&#x27;re handling ultra important, sensitive data there are techniques that have been available for many years (two phase commit, for example) that can help.<p>I love this series but I&#x27;m blown away by how many engineers here automatically assume a system is a failure because it doesn&#x27;t pass a certain type of test from time to time.  I do agree with the series that the marketing materials shouldn&#x27;t claim things, however.  Companies should be honest with what their systems weaknesses currently are.