Scores by kind of claim
Each kind of claim is scored on its own, out of 100: the share that held up, with the range it likely falls in. Fewer resolved claims give a wider range.
-
Factual claims
Statements about the present or the past, checked against the record: did they hold up?
84 79 88 -
Predictions
Statements about events outside the person's control, checked once they fell due: did they come true?
Insufficient record: 2 predictions resolved, 5 needed for a score.
-
Promises
Commitments to the person's or organisation's own future action, with something to deliver: was it delivered?
Insufficient record: 3 promises resolved, 5 needed for a score.
-
Guidance
A company's own figures for its results over a period, checked against what it then reported.
Insufficient record: 1 guidance claim resolved, 5 needed for a score.
All types combined: 84 (likely 79 to 88, high confidence), from 90 claims: 90 factual claims. It mixes kinds of claim in different proportions for different people, so compare people kind by kind.
Jeff Bezos's claims
35 claims
“These implementations are based on the concept of eventual consistency.”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
Amazon's storage system implementations are based on eventual consistency.
Mostly true True in substance, wrong in a detail.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
Judge as of 2011, for the Amazon storage implementations being referred to (e.g., Dynamo, S3 and SimpleDB as described at the time). True: Amazon's documentation or published papers from that period describe those storage systems as eventually consistent by design. Mostly true: the main systems were eventually consistent by default, though some offered optional stronger consistency (e.g., read-after-write for new objects in some regions, or consistent reads as an option). Mixed: roughly half of the referenced systems were eventually consistent. Mostly false: only a minor or narrow system used eventual consistency, presented as the general design. False: the referenced systems were strongly consistent by design in 2011.
Evidence
- Choosing Consistency All Things Distributed (Werner Vogels's blog) · 24 February 2010
“Amazon S3 and Amazon SimpleDB are examples of AWS services that are designed using these high-availability principles using an eventual consistency model.”
- Amazon SimpleDB Consistency Enhancements | Amazon Web Services AWS News Blog (Amazon Web Services) · 24 February 2010
“This flag has a default value of false, so existing applications will continue to use eventually consistent reads.”
- Data Consistency Properties and the Trade offs in Commercial Cloud Storages: the Consumers' Perspective CIDR 2011 (authors from National ICT Australia, UNSW and University of Sydney) · January 2011
“Documentation states that Amazon S3 buckets provide eventual consistency for overwrite put operations [4]”
- Amazon's Dynamo All Things Distributed (Werner Vogels's blog) · 2 October 2007
“Its success in one of the most challenging application environments shows that an eventual-consistent storage system can be a building block for highly-available applications.”
Reasoning
The Dynamo paper describes Dynamo as an eventually consistent storage system (E4), and Amazon's CTO describes S3 and SimpleDB as designed around an eventual consistency model (E1). A 2011 academic paper cites documentation saying S3 gives eventual consistency for overwrite puts (E3). However, in 2010 SimpleDB added an optional consistent-read flag; it was off by default, so reads stayed eventually consistent unless a caller turned it on (E2). The criteria define this case, where the main systems were eventually consistent by default but some offered stronger consistency as an option, as mostly true.
Cite this claim
Jeff Bezos, “Amazon's storage system implementations are based on eventual consistency.” (said 2011). Verdict: mostly true. Reliability API, claim c_844ff163c1ca, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_844ff163c1ca
Claims without a verdict
Is a verdict here wrong, or do you speak for Jeff Bezos? Reply on the claim's own page, with the form at its foot (how replies work). Verdicts are made automatically; how verdicts and scores are made.