DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Maintenance
  4. Amazon Search Outage Offers Two Lessons

Amazon Search Outage Offers Two Lessons

The recent Amazon search outage is a reminder to monitor everything and communicate proactively, implementing simple tactics to keep performance issues from hindering business.

Nilabh Mishra user avatar by
Nilabh Mishra
·
Jun. 06, 16 · Opinion
Like (3)
Save
Tweet
Share
3.38K Views

Join the DZone community and get the full member experience.

Join For Free

The recent Amazon search outage offers two object lessons on the digital customer experience: monitor everything and communicate proactively. Retailers chasing the industry leader can implement a pair of simple tactics to keep performance issues from turning away buyers.

First, the ultimate goal of End-User Experience Monitoring (EUM) is to find a problem before your customers do and fix it before it impacts their experience. Too many sites rely on basic uptime monitoring—sometimes limited to just a home page—to detect slowdowns and outages. This approach would have completely missed an issue like Amazon’s.

Transaction monitoring, on the other hand, would have identified the problem right away. In fact, it did. Here is what the outage looked like from Catchpoint’s vantage point:


On June 2, 2016, users from multiple locations faced issues searching for a product on Amazon’s desktop as well as mobile websites. The problem started around 5:15am EDT and lasted for more than 3 hours, until 8:47am EDT.

While the homepage for the Seattle-based eCommerce company was accessible during this time period, there were problems accessing the ‘Categories’ pages and when searching for products. As you can see below, the HTTP status code returned when accessing the page was 503, or service temporarily unavailable.

AMZN Search_3_705

Adding transaction monitoring to your EUM system—the first lesson here—lets you see and troubleshoot interruptions in processes like these immediately.

The second lesson stems from what customers see during outages. During this time period, Amazon users were greeted with the following error messages:

AMZN Search_4_705

AMZN Search_5_705

These error messages reassure users that Amazon knows about the issue, suggest actions that customers can take to continue shopping, and apologize for a potentially frustrating experience. Communicating like this can prevent complaints from flooding the customer service system, keep buyers on the site and transacting, and avoid a flurry of social media criticism.

But transaction monitoring is the key to identifying problems like these so that customer expectations can be managed. Even better, it can help you resolve problems before customers see them in the first place.

End user Buyer (fashion) Desktop (word processor) Uptime mobile Monitor (synchronization) Media (communication)

Published at DZone with permission of Nilabh Mishra. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Using QuestDB to Collect Infrastructure Metrics
  • A Beginner's Guide to Back-End Development
  • The Role of Data Governance in Data Strategy: Part II
  • Promises, Thenables, and Lazy-Evaluation: What, Why, How

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: