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
43 claims
“The advances in data management developed by Amazon engineers have been the starting point for the architectures underneath the cloud storage and data management services offered by Amazon Web Services (AWS).”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
Data management advances by Amazon engineers were the starting point for the architectures of AWS cloud storage and data management services.
Unresolvable The public record could not settle it.
The second judge would not resolve this claim; 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 or AWS technical sources, or independent technical accounts up to 2011, show that AWS storage and data-management services (such as S3, SimpleDB and EBS) were built on architectures that began with data-management work Amazon engineers did for Amazon's own retail systems, for example Dynamo-derived techniques. Mostly true: this lineage is documented for most of these services, with minor exceptions. Mixed: it is documented for some services but not for others of comparable importance. Mostly false: the link is tenuous, with AWS services mainly built on outside or unrelated architectures and only loosely inspired by internal work. False: the evidence shows AWS storage and data services were not based on internal Amazon data-management advances.
Evidence
- Amazon's Dynamo All Things Distributed (Werner Vogels, Amazon CTO blog) · 2 October 2007 Own record
“Let me emphasize the internal technology part before it gets misunderstood: 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.”
- Dynamo (storage system) - Wikipedia Wikipedia · 11 April 2008 Own record
“The index layer of Amazon S3 implements and extends many core features of Dynamo.”
- A Decade of Dynamo: Powering the next wave of high-performance, internet-scale applications All Things Distributed (Werner Vogels, Amazon CTO blog) · 2 October 2017 Own record
“So, we set out to build a fully hosted AWS database service based upon the original Dynamo design.”
- Dynamo, DynamoDB, and Aurora DSQL brooker.co.za (Marc Brooker blog) · 11 April 2015 Own record
“Instead of replicating across multiple nodes in the ring, in DynamoDB each node consists of a replica group with multiple servers in multiple AZs using Paxos to replicate the data.”
Reasoning
E1 and E2 indicate that S3 draws on Dynamo and similar internal Amazon technology. No evidence item addresses SimpleDB or EBS before 2011, and E3 and E4 are later accounts about DynamoDB. The evidence therefore does not show whether the lineage holds for most of the services the claim names, as the criteria require.
Cite this claim
Jeff Bezos, “Data management advances by Amazon engineers were the starting point for the architectures of AWS cloud storage and data management services.” (said 2011). Verdict: unresolvable. Reliability API, claim c_c97cc0e4fe3b, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_c97cc0e4fe3b
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.