unbelievablethree

Dosya yonetim sistemine giris yapin

{"id":2472,"date":"2017-04-18T13:40:07","date_gmt":"2017-04-18T13:40:07","guid":{"rendered":""},"modified":"2018-05-09T13:38:17","modified_gmt":"2018-05-09T13:38:17","slug":"choosing-right-infrastructure-hadoop","status":"publish","type":"post","link":"https:\/\/cazenasite.com\/?p=2472","title":{"rendered":"Choosing the Right Infrastructure for Hadoop"},"content":{"rendered":"

<\/p>\n

Series: The Hidden Challenges of Putting Hadoop and Spark in Production<\/strong><\/em><\/p>\n

A recent Gartner survey estimates that only 14% of Hadoop deployments are in production. We\u2019re not surprised. We\u2019ve been in many conversations with companies that have been piloting Hadoop to bolster their analytic capabilities beyond relational databases. These companies want to use new distributed processing frameworks, like Apache Spark, which allow them to process data more efficiently, especially data that is inconsistently or variably structured.<\/em><\/p>\n

The pilots typically involve finding a few existing servers within the datacenter and repurposing them to support Hadoop. There is often minimal infrastructure investment for trying out these new technologies, and sometimes, it\u2019s not even an official project.<\/em><\/p>\n

But the stories often continue similarly: The pilot shows promising results, and a series of meetings leads to a set of potential use cases. A project is established, the clock starts ticking, and the realization sets in:  <\/em><\/p>\n

Building a production-grade configuration for Hadoop is a non-trivial exercise. Whether on-premises in a local data center, or in the public cloud, putting Hadoop in production requires expertise and experience to get right.<\/em><\/p>\n

Common challenges fall into a few important categories, which we\u2019ll explore in this blog series:<\/em><\/p>\n