Building a product detail page on Amazon.com calls on between 200 and 300 services.

Judged as of the 2010 letter (published 2011). True: Amazon technical sources from around then (e.g., Werner Vogels's statements, or Amazon architecture papers) state that rendering a product detail page called on between 200 and 300 services, or a figure in that range. Mostly true: a contemporaneous figure is close to the range (e.g., 'over 100', 'up to about 150', or about 300 or more), describing the same page. Mixed: sources give a substantially different figure, or one for a different page or process. Mostly false: the figure is only loosely supported, e.g. from a much earlier period. False: credible technical sources show a count far outside the range (e.g., a few dozen).

Set before the research began.

1. E1 Dynamo: Amazon's Highly Available Key-value Store Amazon.com authors (DeCandia, Hastorun, Jampani, Kakulapati, Lakshman, Pilchin, Sivasubramanian, Vosshall, Vogels), hosted on Princeton course site Own record

   “For example a page request to one of the e-commerce sites typically requires the rendering engine to construct its response by sending requests to over 150 services.”

2. E2 Amazon Architecture - High Scalability - High Scalability (Todd Hoff blog) · 18 September 2007

   “Between 100-150 services are accessed to build a page.”

The Dynamo paper by Amazon engineers, including Werner Vogels [E2], says a page request to one of the e-commerce sites typically sends requests to "over 150 services". A 2007 independent architecture write-up [E3] reports that "between 100-150 services are accessed to build a page." The High Scalability figure dates from 2007, about three years before the 2010 letter; the Dynamo paper is undated in the material. They are close to the claimed 200–300 range but below it, which matches the criteria's description of "mostly true" (e.g., "up to about 150"). Neither source gives a figure in the 200–300 range specifically for a product detail page.