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
“To do so, we’ve leaned heavily on the core principles from the distributed systems and database research communities and invented from there.”
Jeff Bezos, CEO, in shareholder letter 2011 2010 Letter to Shareholders (SEC (Amazon))
Amazon built its storage solutions by leaning heavily on core principles from distributed systems and database research.
Mostly true True in substance, wrong in a detail.
The second judge said resolved true; the verdict shown is the first judge's.
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. True: Amazon's storage systems in use by 2011 (e.g. Dynamo, S3, SimpleDB) were plainly built on established distributed-systems and database research principles and extended them. Evidence would include Amazon's own technical papers (such as the 2007 Dynamo paper citing consistent hashing, vector clocks, quorum and gossip protocols) or independent technical analysis. Mostly true: this holds for Amazon's main storage systems, with a minor detail not supported. Mixed: some Amazon storage systems clearly drew on such research and others were mostly built without it. Mostly false: the link to the research is weak or limited to one minor system. False: evidence shows Amazon's storage systems were developed without relying on that research.
Evidence
- Amazon's Dynamo All Things Distributed (Werner Vogels' blog) · 2 October 2007 Own record
“Dynamo uses a synthesis of well known techniques to achieve scalability and availability: Data is partitioned and replicated using consistent hashing [10], and consistency is facilitated by object versioning [12].”
- Amazon's Dynamo All Things Distributed (Werner Vogels' blog) · 2 October 2007 Own record
“We submitted the technology for publication in SOSP because many of the techniques used in Dynamo originate in the operating systems and distributed systems research of the past years; DHTs, consistent hashing, versioning, vector clocks, quorum, anti-entropy based recovery, etc.”
- Dynamo: Amazon's Highly Available Key-value Store (2007) mwhittaker.github.io (personal paper summary)
“Dynamo is Amazon's distributed higly-available eventually consistent zero-hop distributed hash table (a.k.a. key-value store) that uses consistent hashing, vector clocks, quorums, gossip, and more.”
- Amazon's Dynamo All Things Distributed (Werner Vogels' blog) · 2 October 2007 Own record
“To meet these stringent latency requirements, it was imperative for us to avoid routing requests through multiple nodes (which is the typical design adopted by several distributed hash table systems such as Chord and Pastry).”
Reasoning
Amazon's 2007 Dynamo paper says the system is "a synthesis of well known techniques", naming consistent hashing and object versioning (E1). Werner Vogels' blog post introducing the paper says many of Dynamo's techniques "originate in the operating systems and distributed systems research", including DHTs, vector clocks, quorum and anti-entropy (E2). An independent summary confirms that Dynamo uses consistent hashing, vector clocks, quorums and gossip (E3). The paper also describes a deliberate change from the multi-hop routing used in research systems like Chord and Pastry (E4), which fits the claim that Amazon "invented from there." However, the evidence covers only Dynamo, not S3 or SimpleDB, so it supports the claim for one main system rather than for all of Amazon's storage systems.
Cite this claim
Jeff Bezos, “Amazon built its storage solutions by leaning heavily on core principles from distributed systems and database research.” (said 2011). Verdict: mostly true. Reliability API, claim c_135801eaec53, method 0.1.0+c876030c. https://epistacklabs.com/claims/c_135801eaec53
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.