Visual Studio Code 1.7 overloaded npmjs.org, release reverted

Post by andyburke » Thu, Nov 03, 2016, 1:48 AM UTC

Post by meira » Thu, Nov 03, 2016, 1:54 AM UTC

Post by hyperliner » Thu, Nov 03, 2016, 2:01 AM UTC

akfish wrote: post #5

Which is more possible? A bug or they just underestimated the volume of traffic that could be caused by ATA in real life?

Post by CaveTech » Thu, Nov 03, 2016, 2:09 AM UTC

mavsman wrote: post #7

If I were on the Azure team I'd be offering tons of free credit to npmjs.org to get them to use Azure. Azure coming to the rescue would be the perfect ending to this story for Microsoft.

Post by azinman2 » Thu, Nov 03, 2016, 2:13 AM UTC

CaveTech wrote: post #8

mavsman wrote: post #7

If I were on the Azure team I'd be offering tons of free credit to npmjs.org to get them to use Azure. Azure coming to the rescue would be the perfect ending to this story for Microsoft.

I don't think most organizations could relaunch their infrastructure on a totally different stack at the drop of a dime. And if it was really a "throw more servers at it" problem then it wouldn't really matter who was hosting them, would it?