Clare Avieli is the Director of Product Marketing at CA BlazeMeter, where she leads the digital marketing team. She has 15+ years of experience in marketing, PR, and writing, with a specialization in technology. Prior to CA BlazeMeter, Clare led the online and content marketing strategy at Panaya (now Infosys) and was the marketing manager at Nolio, now CA Release Automation.

Learn JMeter in 5 Hours

Start Learning
Slack

Run massively scalable performance tests on web, mobile, and APIs

What We Should Learn From Apple’s iPhone 6 Web Failure

It was the biggest event on Apple’s 2014 calendar; the long awaited launch of the iPhone 6.

 

On September 9, Apple announced the iPhone 6, the 6 plus and its new smartwatch. Apple fans had been camping outside the Fifth Avenue store for days in anticipation of the release. On the day itself, thousands flocked to the web to watch a live stream of CEO Timothy Cook unveil Apple’s latest innovations.

 

But instead of Apple’s new products, many visitors saw the following message…

 

…over and over again.

 

The story was the same across the web.  Chrome, Safari, Firefox, OSX and MS all displayed the same message.

 

So what can we learn from Apple’s Web Failure?

 

September the 9th was essentially Apple’s ‘Black Friday’ – one of its most important days of the year. Extremely high traffic to the site on this day was inevitable and, as a result, there couldn't have been a worse time for a web failure to occur.

 

With Black Friday coming up, you need to ensure that this won’t happen to your site. After all, if it can happen to Apple, it can happen to anyone!

 

Fortunately, there are steps that you can take during your load testing to ensure that your web or app won’t fail under extremely heavy traffic loads. In my last blog post, I covered the key questions to ask yourself when running performance testing prior to a big online event.

 

Here I’d like to go one step further by saying that there are certain steps that you must include in your load testing to avoid failures. These include:

 

1.     Making sure you bring your system into the failure – so you know what will fail, when it will fail and how it will fail

2.     Finding your critical resources ahead of time

3.     Observing your application logs

4.     Checking your third party integrations

5.     Tracking your end-user performance

6.     Running load tests from the production environment

7.     Setting up back-up servers and locations

 

 

You might also be interested in viewing our on-demand webcast, Load Testing Your Shopping Cart in 30 Minutes, in which we cover all the points above, mistakes to avoid and best practices on preparing for a big event.

 

Also, please share your thoughts, experiences and questions with me in the comments box below.

 

 

 

You might also find these useful:

Interested in writing for our Blog?Send us a pitch!

Your email is required to complete the test. If you proceed, your test will be aborted.