What Is Hadoop?
Apache Hadoop is an open-source framework, originally created by Doug Cutting and Mike Cafarella and inspired by Google's GFS and MapReduce papers, that lets you store and process petabyte-scale datasets across clusters of ordinary servers. It bundles three core components: HDFS (Hadoop Distributed File System) for storage, YARN (Yet Another Resource Negotiator) for cluster resource management, and MapReduce as the original processing engine, all designed to tolerate hardware failure as a normal, expected event rather than an exception.
Cricket analogy: Like the IPL auction pooling players from many franchises into one shared system, Hadoop pools cheap commodity servers into one cluster — CSK's success wasn't built on one superstar; Hadoop doesn't need one supercomputer, just many ordinary nodes working together.
Why Hadoop Was Created
Before Hadoop, scaling data processing meant buying ever-bigger single machines (vertical scaling), which became prohibitively expensive and hit physical limits. Hadoop instead scales horizontally: add more commodity nodes to the cluster, and both storage capacity and processing power grow roughly linearly, at a fraction of the cost of specialized enterprise storage arrays.
Cricket analogy: Choosing to build a squad of 15 solid all-rounders rather than paying for one $2 million superstar in the IPL auction reflects horizontal scaling — Hadoop clusters bet on many affordable nodes rather than one prohibitively expensive server.
Core Design Principles
Hadoop's defining idea is "move computation to the data" rather than moving data to computation — since network bandwidth is often the bottleneck at scale, code is shipped to the data node that already holds the relevant HDFS block, and results are aggregated afterward. Combined with 3x block replication by default, this gives Hadoop resilience: if a node dies mid-job, the scheduler reschedules the failed task on a node holding a replica, without operator intervention.
Cricket analogy: When a fielder is injured mid-over, the 12th man substitutes seamlessly without stopping the match — Hadoop's fault tolerance works the same way, rerouting a failed task to a node holding a replicated copy of the data.
# Basic HDFS interaction
hdfs dfs -mkdir /user/data
hdfs dfs -put localfile.txt /user/data/
hdfs dfs -ls /user/data
hdfs dfs -cat /user/data/localfile.txtWhere Hadoop Fits Today
Hadoop's original MapReduce engine is largely legacy in modern pipelines — most teams still run HDFS as a data lake foundation but use Apache Spark for actual processing because Spark keeps intermediate data in memory rather than writing to disk between every map and reduce stage, making iterative workloads much faster.
- Hadoop is an open-source framework for distributed storage (HDFS) and processing, inspired by Google's GFS and MapReduce papers.
- It was created by Doug Cutting and Mike Cafarella and named after Cutting's son's toy elephant.
- Hadoop scales horizontally across commodity hardware instead of relying on one expensive high-end machine.
- Its core principle is moving computation to the data to minimize network bottlenecks.
- HDFS replicates each block (default 3x), so the cluster tolerates individual node failures automatically.
- YARN separates resource management from job scheduling, letting frameworks beyond MapReduce run on the same cluster.
- Many modern pipelines still use HDFS as a storage layer while running Spark instead of classic MapReduce for processing.
Practice what you learned
1. Which three components make up the traditional core of Hadoop?
2. What is the default HDFS block replication factor?
3. What design principle explains why Hadoop ships processing code to the node holding the data?
4. Which paper(s) most directly inspired Hadoop's architecture?
5. In many modern data platforms, what commonly replaces classic MapReduce for processing while HDFS still handles storage?
Was this page helpful?
You May Also Like
The Hadoop Ecosystem
A tour of the major projects that surround core Hadoop — Hive, Pig, HBase, Sqoop, Flume, ZooKeeper, and Oozie — and how they fit together.
Hadoop Daemons
What NameNode, DataNode, ResourceManager, NodeManager, and the other Hadoop background processes actually do, and how they interact.
Setting Up a Hadoop Cluster
A practical walkthrough of planning and configuring a Hadoop cluster, from single-node pseudo-distributed setups to multi-node production layouts.
Related Reading
Related Study Notes in Programming
Browse all study notesApache Spark Study Notes
Programming · 30 topics
ProgrammingApache Flink Study Notes
Programming · 30 topics
ProgrammingSnowflake Study Notes
Programming · 30 topics
ProgrammingApache Airflow Study Notes
Programming · 30 topics
Programmingdbt (Data Build Tool) Study Notes
Programming · 30 topics
ProgrammingPowerShell Study Notes
Programming · 30 topics