Earlier quoted context omitted.
Did the math, that's about 7 billion searches a day. That doesn't sound like a lot.
I mean, google does 8.5 billion per day. What would be a lot to you?
How Amazon uses chaos engineering to handle 80k requests per second
11–20 of 119 posts
Re: How Amazon uses chaos engineering to handle 80k requests per second
#12I feel like Amazon search is one of the worst products I've ever used. It is a clusterf/ck of paid advertisements and obviously gamed results. I don't care how many requests/sec you get. If the results are horrible, what does it matter?
I'm at the point that I rarely ever buy products on Amazon anymore. It's a total disgrace. On an ethical level, I wish I had the ability to say "I only want to be presented with results that weren't made in China or other slave societies".
Re: How Amazon uses chaos engineering to handle 80k requests per second
#13If it's the real-deal, and not like people saying "Bun.js can serve 65k req/s+ (cough cough to localhost,)" that's impressive.
But I never see anyone talk about real-world numbers. Just synthetic poopoo.
I think I read the article correctly, but I think it only talks about how they introduce "chaos engineering," I didn't recall them talking about how they actually handle a volume of traffic like 80k req/s.
Re: How Amazon uses chaos engineering to handle 80k requests per second
#14Surprised that 80K/second is called "massive" for Amazon.com's main search feature.
Re: How Amazon uses chaos engineering to handle 80k requests per second
#15I feel like Amazon search is one of the worst products I've ever used. It is a clusterf/ck of paid advertisements and obviously gamed results. I don't care how many requests/sec you get. If the results are horrible, what does it matter?
Re: How Amazon uses chaos engineering to handle 80k requests per second
#16I would love to know what software stack, hardware, and uplink connections in total they utilize to accomplish a real-world 80k request per second throughput. How many instances do you guys think Amazon runs for its primary e-commerce front-end stack? In total, and per region? Assuming they have a multi-region rollout. If it's the real-deal, and not like people saying "Bun.js can serve 65k req/s+ ( cough cough to loc…
The number probably changes all the time based on load. They'll never release these details because it's a competitive advantage to have the "how popular are they in $place at $time-of-day" data private.
When they do share numbers, it'll always be the most flattering and devoid of any context beyond the "wow" factor.
Re: How Amazon uses chaos engineering to handle 80k requests per second
#17Re: How Amazon uses chaos engineering to handle 80k requests per second
#18I feel like Amazon search is one of the worst products I've ever used. It is a clusterf/ck of paid advertisements and obviously gamed results. I don't care how many requests/sec you get. If the results are horrible, what does it matter?
Re: How Amazon uses chaos engineering to handle 80k requests per second
#19I feel like Amazon search is one of the worst products I've ever used. It is a clusterf/ck of paid advertisements and obviously gamed results. I don't care how many requests/sec you get. If the results are horrible, what does it matter?
Is there any alternative front end for Amazon? AI with some image-similarity smarts could do a much better job grouping/de-duping similar products.