Under Armour

Under Armour is a leading developer, marketer and distributor of branded performance apparel, footwear and accessories. Founded in 1996 by a former University of Maryland football player, Under Armour today generates more than $2 billion in annual sales through an array of retailers and, increasingly, direct to consumers through the Under Armour online shop.

The Problem

In 2011 the company determined that its online store needed an upgrade to better reflect the Under Armour brand. The previous Ecommerce site (known as Version 4 or “V4”) had been in service since 2007, and although successful, was beginning to show its age. Under Armour needed to address limitations with its existing content management system, and to redesign the UI to better reflect the company’s brand and improve the overall shopability of the site. Under Armour was determined to complete this upgrade in time for the 2011 holiday shopping season.

In addition to the CMS and UI concerns, site scalability needed to be addressed in order to meet the demands of this high growth business. The primary scalability issue with the previous platform was the SQL Server database.

The Solution

After the company evaluated a number of commercial ecommerce solutions, Under Armour felt that building a custom solution was the option that offered the best chance to hit their tight timelines with a site that met their needs. With only eight months to design, test and deploy its new online store, Under Armour turned to MongoDB as the heart of its custom-built Ecommerce platform.

The primary advantages of a custom build included the opportunity to re-use some components of the previous platform, the ability to directly control the implementation and course correct along the way, and the proven track record of their internal technology team in building and supporting the site. In addition, the level of customization needed to meet the company’s requirements negated many of the advantages of “off the shelf” commercial solutions.

Given that it was attempting an 18-month project in less than half that time, Under Armour needed to maintain a high degree of control while relying on a known and proven approach.

Why MongoDB?

After considering a range of NoSQL systems, Under Armour chose MongoDB as the underlying database. MongoDB’s inherent ability to support multi-data center replication and sharding addressed Under Armour’s disaster recovery and scalability needs. The dynamic schema of MongoDB was particularly attractive to the development team. And MongoDB’s high performance on both reads and writes was the final piece of the puzzle.