Beyond MapReduce
summary
MapReduce on Hadoop delivers cost‑effective scalability but proves batch‑oriented not real‑time: joins and iterative graph algorithms are awkward, and MapReduce forces heavy JVM churn and disk I/O. Practical fixes: higher‑level layers (Hive, Cascading/Scalding) reduce boilerplate; Spark speeds analytics by caching in memory; Storm handles low‑latency event streams; Pregel/BSP style systems and Titan address graph workloads. Middle‑sized datasets (1–10 TB) benefit from lighter‑weight, fine‑grained, collection‑centric tools rather than raw Java MapReduce.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:48Trends
- 12:48Word Count
- 18:40Challenge with Mapreduce
- 20:35The Google File System
- 24:50Disadvantages
- 28:44Dremel
- 31:18Scalding
- 34:09Alternatives To Cascading and Scalding
- 35:31The Spark Code
- 38:48Bulk Synchronous Parallel
related talks
44mData Science at Scale with Apache Spark
45mFrom Big Data to Fast Data: Apache Spark
30mScalability Challenges in Big Data Science
45mSolving Real & Big (Data) Problems Using Hadoop
31mML practices in the industry
11mHow Companies are Using Spark, and Where the Edge in Big Data Will Be
37mBig Data Analytics, Machine Learning, Real Time Processing
01h 25mApache Spark for Big Data Processing
