Analytics in the cloud: 5 lessons learned
- 16 June, 2009 01:31
Every company-from the smallest start-up to the largest firm-needs to be agile in today's market to respond to changing dynamics and new competition. But these days it's often the smaller companies who are better positioned to adapt: as the barriers to entry have decreased, emerging companies now have access to data streams-and techniques for analyzing them-that used to be the exclusive province of the largest companies. At the same time, the CIOs of larger organizations now find themselves as much bound by their legacy systems and data as they are empowered by them. The costs of managing these legacy systems are getting in the way: too much of the budget goes to maintenance, and not enough is left over for new development and technologies.
Nowhere is this dynamic more apparent than with Business Intelligence (BI). As BI once again rises to the top of priority and wish lists, CIOs are struggling with the costs of meeting internal demands while keeping within their budgets, and still finding time for innovation. The costs of proprietary servers and storage devices, as well as the space and energy to manage them, are off the charts and highly visible to every CFO, CTO and procurement professional. Proliferating copies of data into multiple one-off analytical systems-seemingly one for every question to be asked-only adds to the costs, and even new "data appliances" can cost in the tens of millions to scale up as requirements grow.
Clearly, new approaches are needed to cost-effectively scale BI systems while meeting the demand for information on the front lines. Here are some examples of how forward-looking organizations are doing large-scale analytics in the cloud to break the logjam.
1. Hold the line with commodity hardware.
Most new analytic data engines run on inexpensive commodity hardware, transforming IT cost models and conventional wisdom about the costs of new systems. As Mark Dunlap, a consultant with Evergreen Technologies and a veteran of massive data warehouse projects at Amazon and Fox Interactive, puts it, "If you're using proprietary hardware, you're in a losing battle. Sooner or later, whatever company's developing that technology will not be able to keep up. We've seen it over and over and over again-they won't keep pace with what commodity systems are doing."
2. Buy capacity when you need it, not according to a closed appliance size
Clint Johnson, VP of Business Intelligence at Zions Bancorporation, says he's avoiding locked-in purchase models as they tackle massive data challenges. "We like the ability to add hardware easily, incrementally," says Johnson. "Specialized appliances we looked at scaled in very specific size increments." Not only are those new purchases large, they may be substantially greater than near-term needs-but payment is not scaled to usage, it's by total capacity.
3. Unused server power is a priceless resource -- use it.
Typical capacity utilization rates on distributed servers used for BI applications or data marts are often at 20 percent or below, leaving substantial system power unused. Newer software can harness that power with effective provisioning strategies. Brian Dolan, Director of Research Analytics at the Fox Audience Network, says, "With my Greenplum [cloud-based] database, I get to share 40 nodes with the production system. I use them when I need them, and then I give them back." Building "sandboxes" as needed-mapping servers (or cores) and data stores into the form needed-addresses the task at hand efficiently. A well-designed server pool, with the right software for flexible provisioning, becomes your internal "cloud."
4. Keep asking, keep changing -- and keep the data.
New practices in BI are echoing the "agile" methodologies programmers are finding effective. Complex techniques, statistical analyses, and new analytical models emerge and disappear. For example, Ryan Hawk, T-Mobile Director of Information Management, and his analytics team needed to build models of telecom usage-propensity to churn, revenue generation, and more- but were challenged because "data is a business case-we have to decide what we can afford to store on our MPP systems," Hawk says. "The hardest thing is having to purge data every 60 days-you can't do much trending."
By shifting their data warehouse into an agile, virtualized infrastructure, T-Mobile now has flexible access to more data and can analyze and rethink at will. Like Fox, they're able to build analytical "sandboxes" on-demand to discover new questions. Grab data to explore those questions. Tear it down, and do it again. Data is the other element of the "cloud;" keep it where you need it, and use as appropriate.
5. Run programs "close to the data."
Dolan's team at Fox might work with two weeks' worth of data: 100 billion lines, 10s of terabytes. Exporting, transforming, moving and distributing that data in chunks (extract, transform and load: ETL style), constrained by bandwidth and system load factors, used to take 3 to 4 days. Rebuilding all the joins, indexes and other structures within the data would consume another day or two. But with new in-database analytics technology, Fox can run programs directly in the database, eliminating the bottlenecks standing between his team and business insights. According to Dolan, "Inside our Greenplum database, setting up two weeks' worth of data takes us about 20 minutes."
Exploiting information has become an imperative for all businesses, and this continues to become even more important as data growth accelerates and new streams of precious information emerge. Supporting the teams who will provide agile response is a competitive necessity.
Merv Adrian is principal at consulting firm IT Market Strategy.