Tech
The HTTP client with no timeout that took down four services
A recommendations service, which is genuinely optional, started responding slowly. Not failing. Responding, in ninety seconds instead of eighty milliseconds. Within four minutes the product catalogue was down, then checkout, then the mobile API. An optional feature took out the entire storefront, and the recommendations service never once returned an error.
The catalogue called recommendations with a client constructed as a default instance. No connect timeout, no socket timeout, because the ...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to