Thanks! Amazon TOS allows caching. But, not sure if there is any specific restriction on shared cache.
Yes. Browse Nodes are essentially product categories. So, users search for the same set of categories. There are ~40K browse nodes in each Amazon domain and we have cached most of them already [1]. So, the cache miss is…
Not really! Lets say, user 1 makes an API call to our server to fetch browse node: 1000 (Books). The first time such request is made, our server will make an API call to Amazon using user 1's AWS key. Once we get the…
No. I don't store your API key (i.e. awsSecret). I only cache the product data to serve other users: https://browsenodes.com/how-to-solve-requestthrottled.html Hope that helps!
When I was building a price comparison site using Amazon Product Advertising API, I ran into this throttling error frequently: "You are submitting requests too quickly. Please retry your requests at a slower rate." So,…
Thanks! Amazon TOS allows caching. But, not sure if there is any specific restriction on shared cache.
Yes. Browse Nodes are essentially product categories. So, users search for the same set of categories. There are ~40K browse nodes in each Amazon domain and we have cached most of them already [1]. So, the cache miss is…
Not really! Lets say, user 1 makes an API call to our server to fetch browse node: 1000 (Books). The first time such request is made, our server will make an API call to Amazon using user 1's AWS key. Once we get the…
No. I don't store your API key (i.e. awsSecret). I only cache the product data to serve other users: https://browsenodes.com/how-to-solve-requestthrottled.html Hope that helps!
When I was building a price comparison site using Amazon Product Advertising API, I ran into this throttling error frequently: "You are submitting requests too quickly. Please retry your requests at a slower rate." So,…