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
“by relaxing the synchronization requirements of updates that need to be disseminated to large numbers of replicas, these systems are able to survive under the harshest performance and availability conditions.”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
The storage systems Amazon has pioneered relax synchronization requirements for updates that need to be disseminated to large numbers of replicas, which lets them survive under the harshest performance and availability conditions.
Mostly true True in substance, wrong in a detail.
The second judge said resolved true; the verdict shown is the first judge's.
The evidence is the person's or their organisation's own records.
Said for an organisation they lead or work for; it counts on both records.
What would count as true or false
True: Amazon technical publications or documentation from around 2011 or earlier (such as the 2007 Dynamo paper, AWS documentation, or engineering talks) show that Amazon storage systems used relaxed synchronization or eventual consistency for propagating updates to many replicas, explicitly to keep high availability and performance under adverse conditions such as failures or heavy load. Mostly true: such a design is documented for some major Amazon storage systems, but the stated motive or scope is somewhat overstated. Mixed: relaxed consistency is used in some systems, but its link to surviving harsh conditions is weak or disputed. Mostly false: Amazon's systems mainly relied on strongly synchronized replication, with relaxed consistency only marginal. False: the evidence shows Amazon's storage systems did not relax replica synchronization.
Evidence
- Amazon's Dynamo All Things Distributed (Werner Vogels blog; reproduces the SOSP'07 paper by Amazon.com authors) · 2 October 2007 Own record
“For systems prone to server and network failures, availability can be increased by using optimistic replication techniques, where changes are allowed to propagate to replicas in the background, and concurrent, disconnected work is tolerated.”
- Amazon's Dynamo All Things Distributed (Werner Vogels blog; reproduces the SOSP'07 paper by Amazon.com authors) · 2 October 2007 Own record
“Dynamo is designed to be an eventually consistent data store; that is all updates reach all replicas eventually.”
- Amazon's Dynamo All Things Distributed (Werner Vogels blog; reproduces the SOSP'07 paper by Amazon.com authors) · 2 October 2007 Own record
“Fourth, Dynamo is built for latency sensitive applications that require at least 99.9% of read and write operations to be performed within a few hundred milliseconds.”
- Amazon's Dynamo All Things Distributed (Werner Vogels blog; reproduces the SOSP'07 paper by Amazon.com authors) · 2 October 2007 Own record
“Dynamo is not directly exposed externally as a web service; however, Dynamo and similar Amazon technologies are used to power parts of our Amazon Web Services, such as S3.”
Reasoning
The 2007 Dynamo paper by Amazon authors, a technical publication the criteria name, describes Dynamo as an eventually consistent store in which "all updates reach all replicas eventually" (E2). It says optimistic replication, with changes propagating to replicas in the background, increases availability in systems prone to server and network failures (E1). It also states latency targets for that design (E3). The evidence documents this design in detail only for Dynamo. It says only that Dynamo and "similar" technologies power parts of AWS such as S3 (E4), and it does not address "large numbers" of replicas or the "harshest" conditions, so the claim's full scope is not shown.
Cite this claim
Jeff Bezos, “The storage systems Amazon has pioneered relax synchronization requirements for updates that need to be disseminated to large numbers of replicas, which lets them survive under the harshest performance and availability conditions.” (said 2011). Verdict: mostly true. Reliability API, claim c_55ae92386c84, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_55ae92386c84
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.