Quantcast StorefrontBacktalk » Blog Archive » What Was Wal-Mart Thinking When It Made Key Site Changes On Black Friday?
advertisement
advertisement

What Was Wal-Mart Thinking When It Made Key Site Changes On Black Friday?

Written by Evan Schuman
December 3rd, 2008
Like this story? Share it
To share this story with people in your social network, please click on the network icons below.

At about 6 AM New York time on Black Friday (Nov. 28), Wal-Mart’s site went down for about an hour and then came back up. But this time, the company had moved its content pages to an outside service. Wal-Mart said this was a scheduled change, a concept that Gareth Evans, head of client services at Web tracking firm Sitemorse, finds unlikely.

"We saw where they suddenly shifted all of their, presumably, image content over to Akamai on the morning of Black Friday," Evans said. "Now that’s a really odd thing to do, you know? Hey, it’s a really big day. Let’s make a major change to our infrastructure without testing it. What if that had gone wrong? As it happens, they were OK once it came onstream, but they had no idea whether that was going to benefit them or be detrimental. They turned it on at 7 o’clock in the morning."

Evans made his comment as part of a podcast discussion on how E-tailers fared during 2008’s Black Friday and Cyber Monday. Also on the panel: Shawn White, director of external operations at Keynote; Imad Mouline, CTO for Gomez; and Peter Alguacil, analyst for Pingdom. StorefrontBacktalk Editor Evan Schuman moderated the discussion.


advertisement

2 Comments | Read What Was Wal-Mart Thinking When It Made Key Site Changes On Black Friday?

  1. Dan Shields Says:

    Maybe they just think they were smarter then what they were and wouldn’t have any problems. You would think they at least would of done it around 2am.

  2. Shawn White Says:

    Another possiblity, not yet considered, is that Walmart did *indeed* test this change days prior and simply decided to deploy the change when they did. Granted, I would agree with the previous comment that doing so earlier in the day would have allowed for more time to recover or revert back had it introduced any problems…which it did not by-the-way.

Leave a Reply

Newsletter

Quickly catch-up on the latest in E-Commerce and Retail Tech with our free weekly newsletter, with urgent bulletins as news merits.
advertisement

Most Recent Comments

Kill All The Passwords

This article does mention, but does not give enough attention to, the fact that the attacks discussed are only feasible when the encrypted password file can be copied and subjected to an offline attack. The trick is to have authentication performed on a separate, much more strongly secured host - such as an Active Directory Domain Controller, or a Kerberos server, or a NIS+ server, or even using something as banal as an LDAP-over-SSL authentication dialog. In these environments, the odds of the "password file" being stolen and subjected to an offline attack go to near zero, and only online attacks may be carried out by the attacker. With sensible exponential backoff between failed password attempts, lockout after a modest number of failed attempts on a single account, and pattern detection, that minimum 7 character password is quite secure enough. Passwords aren't dead yet for security purposes, and they will be with us for a very long while to come for practical purposes. The trick is to employ them correctly. Read more...
The possibilities you describe are years away from being implemented at best, so for the moment passwords are an ugly reality. Luckily, password managers can easily manage hundreds of passwords of any length. The only thing a user needs to remember is the master password. It seems like an easier task to educate users on how to use password managers rather than implement complex security technology on a global basis. Read more...