6 ms·

If I'm reading their post-outage actions correctly, they certainly align with availability > durability. There are many things to like about DynamoDB, but one

If I'm reading their post-outage actions correctly, they certainly align with availability > durability. There are many things to like about DynamoDB, but one of the things I really dislike is the 'abscence of an error == success' pattern that they implement for many operations. With less frequent metadata requests, I imagine there is a greater chance of silent failures (ie availability looks fine, durability is gone). Could be wrong though, I'm not going to pretend to know more about distributed systems than the DynamoDB developers.

senderista 11y ago
Durability is certainly not being compromised. I think they are just referring to increasing lease times. Timeouts are always a tradeoff (false alarm frequency vs. recovery time), and this event has prompted them to re-evaluate the tradeoff. If you suspect the design of DynamoDB is sloppy, I encourage you to read this: http://cacm.acm.org/magazines/2015/4/184701-how-amazon-web-services-uses-formal-methods/fulltext http://cacm.acm.org/magazines/2015/4/184701-how-amazon-web-s...