At Amazon every 100ms latency cost 1% of sales. Here's what we did
twitter.com
twitter.com
Since the start of the pandemic I was ordering groceries from Amazon Fresh.
Adding/removing an item to/from cart takes couple seconds at very least. Expanding “similar items” can take up to ten seconds easily.
It seems at times like they are using a blockchain or maybe a real human writes down my order on a piece of paper (and sometimes they have to run for a new pen).
This is not a one-time experience or a rush hour. It always works like this, it’s just how it is built.
Your experience with Amazon Fresh does not correlate to the main Amazon front end.
Disclaimer: I work at AWS, but not in any department directly related to the Amazon website itself or Amazon Fresh. However, I have learned some things about how they build their systems behind the scenes.
>http://amazon.com is server side rendered and has no client side rendering framework. The potential latency hit didn't justify it.
>We were stuck with jQuery 1.6.4 Grimacing face
>SSR React wasn't fast enough for us. This blew my mind.
While SSR has gotten some more support in the past 1-2 years, This is not going to sit well with majority of HN crowds.
One thing I really want to see is some sort of predictable latency rendering. Every page should render at fixed predetermined timing regardless latency ( Subject to Network latency difference so everyone would have different value ) . I dont like webpage that some times load so fast it felt it is punching me to the face while some links of it takes 3s to load.
But you and I are just two customers out of the hundreds of millions that I presume they serve on a daily basis, and they can only work on their average, median, P90, P99, and P99.99 results.