A Strong ARM for Big Data (Datanami – Sponsored Content by Calxeda)
From the post:
Burgeoning data growth is one of the foremost challenges facing IT and businesses today. Multiple analyst groups, including Gartner, have reported that information volume is growing at a minimum rate of 59 percent annually. At the same time, companies increasingly are mining this data for invaluable business insight that can give them a competitive advantage.
The challenge the industry struggles with is figuring out how to build cost-effective infrastructures so data scientists can derive these insights for their organizations to make timely, more intelligent decisions. As data volumes continue their explosive growth and algorithms to analyze and visualize that data become more optimized, something must give.
Past approaches that primarily relied on using faster, larger systems just are not able to keep pace. There is a need to scale-out, instead of scaling-up, to help in managing and understanding Big Data. As a result, this has focused new attention on different technologies such as in-memory databases, I/O virtualization, high-speed interconnects, and software frameworks such as Hadoop.
To take full advantage of these network and software innovations requires re-examining strategies for compute hardware. For maximum performance, a well-balanced infrastructure based on densely packed, power-efficient processors coupled with fast network interconnects is needed. This approach will help unlock applications and open new opportunities in business and high performance computing (HPC). (emphasis added)
I like powerful hardware as much as the next person. Either humming within earshot or making the local grid blink when it comes online.
Still, hardware/software tools for big data need to come with the warning label: “Semantics not included.”
To soften the disappointment when big data appliances and/or software arrive and the bottom line stays the same, or gets worse.
Using big data, or rather effective use of big data, that is improving your bottom line, requires semantics, your semantics.