AppDynamics helped manage performance in a dynamic environment
With more than 10 petabytes of data, the FamilySearch service was a challenge to manage, especially as it grew. “We're growing the system at an incredibly fast pace of 300 million new records per year and 300 million new images,” said Bob Hartley, Principal Engineer and Development Manager at FamilySearch. “We're on the path to 20 petabytes of data, and more.” FamilySearch started out with an Oracle database, Java and Enterprise JavaBeans (EJB) to power its search engine, but quickly found that this architecture could not support the data. “The amount of time it took to query the database against 3 billion records to return one record was just completely unacceptable to users,” Hartley said. “They don't want to wait minutes.” FamilySearch quickly realized that simply scaling infrastructure was not an efficient way to manage performance and would be prohibitively expensive. They needed to find a way to maximize application performance while the load and data grew exponentially.