
MapReduce
Computer programWikipedia
34
MENTIONS
14
EPISODES
14
PODCASTS
Search complete. 34 mentions across 14 episodes found for "MapReduce".
Oct 19, 2026
21. Dynamic Workflows at Scale (Escaping the AI Chat Window Bottleneck)
S
14:08speaker_0HOST
Okay.
S
14:09speaker_1HOST
If you write a traditional MapReduce style script to process 100 files through a three-step process, audit, verify, report, the script will typically wait for all 100 files to finish the audit phase.
S
14:21speaker_0HOST
Like an artificial barrier.
S
14:22speaker_1HOST
Exactly.
Unlocking the Future of Cybersecurity: Yan Solihin, Pegasus Professor at University of Central Florida
S
58:30Stephen IbarakiHOST
fellows, Sanjay and Jeff, and they both left, right? And in fact, they even saved Google in the year 2000, right, when Google's search engine had a problem.
S
58:43Stephen IbarakiHOST
And every major kind of technical achievement, including MapReduce, They left.
Y
58:53Yan SolihinGUEST
Yeah.
S
58:55Stephen IbarakiHOST
So, you know, we can say in the interim, we have these sort of goals we want from an education standpoint.
P
Unknown podcast
Anthropic's Claude Traces NIST Curve Seeds to a 1997 Unix Clock
Oct 17 · 1 Mention
S
14:57speaker_1HOST
Instead of drawing your sub-agent topology by hand, A lead agent plans the task and spins sub-agents up and down in phases, with fan-out and fan-in.
S
15:06speaker_1HOST
The talk says Claude Code uses a JavaScript engine for MapReduce-style jobs.
L
15:11Lenar KessHOST
They open with history.
L
15:12Lenar KessHOST
Ken Thompson built Unix in a month.
Sam Newman on Software Factories: Why AI Can't Fix Your Production Incidents (Yet)
S
11:10Sam NewmanGUEST
And so literally, it-- when a computer g- fails, the software doesn't really care.
S
11:15Sam NewmanGUEST
I mean, this is way back in the days of MapReduce, right? You'd slide a tray out.
S
11:18Sam NewmanGUEST
You'd find, okay, that's the hard drive.
S
11:20Sam NewmanGUEST
You'd unzip the Velcro, throw it in a bin, put another hard drive in, tape on the Velcro, put it in.
John Platt (Google): AI for Climate and Science
J
2:30John PlattGUEST
It could be a very data-heavy problem because people at Google are very, very good at large data processing.
J
2:37John PlattGUEST
I mean, dating back to MapReduce and all of the large-scale computing that we have.
J
2:42John PlattGUEST
And now we have lots of TPUs and AI.
J
2:45John PlattGUEST
So if there's problems that we think are... scientific problems where AI can do very, very well, then we try to attack those.
Watch now | Recording of AURA - Chris Gambill & Shane Gibson on 9th October 2026
C
60:06Chris GambillGUEST
Well, now we have AI.
C
60:09Chris GambillGUEST
So it makes those things all of a sudden possible and kind of in the window of opportunity again, which increases that mountain of work, right? That's what big data did, right? That's what Hadoop and MapReduce did, right? It increased the mountain of work.
C
60:23Chris GambillGUEST
It never decreased the mountain of work.
C
60:26Chris GambillGUEST
That's what cloud compute did.
Voice AI Agents: Testing, Trust, and Scale
B
15:16Brooke HopkinsGUEST
So I like to kind of take a similar task and break it down into like paralyzed.
B
15:20Brooke HopkinsGUEST
It's like MapReduce, but for humans, it's like break it down into a bunch of parallel workflows that you're like still working on the same thing, but it's doing different pieces.
B
15:29Brooke HopkinsGUEST
And so you're kind of like checking in on different pieces of it.
A
15:32Amir BormandHOST
Absolutely.
Machine Learning Systems: Designs that scale
S
3:24speaker_4HOST
If you look back, we used to rely on these incredibly clunky JVM-based Hadoop tools to do the heavy data lifting.
S
3:30speaker_3HOST
And Hadoop relied on MapReduce.
S
3:32speaker_4HOST
Exactly.
S
3:32speaker_3HOST
Yeah.
David Crawshaw: From Tailscale to exe.dev, and Why AI Agents Need Their Own Computers
D
19:28David CrawshawGUEST
I, I wanted to do something with lots of computers or very large computers because all of my work had been basically solo open source stuff, which meant my universe was constrained to the PC or the Mac or some machine on that scale.
D
19:43David CrawshawGUEST
And, uh, I had recently been doing a data analysis project with my now father-in-law, who's a professor at Haas, and, you know, I'd, I'd built this thing because the data set didn't fit in one machine, and so we found 10 machines somewhere at the university, and I, I tried to build something across them and, you know, hacked up some very crude MapReduce-looking thing-
M
20:01Matt KleinHOST
Yeah
D
20:02David CrawshawGUEST
... based on what I'd read about MapReduce.
Beyond the Pipeline: AI, Metadata, and Autonomous Data Systems
M
8:00Michael SlaterGUEST
Right.
M
8:01Michael SlaterGUEST
And then we had Spark and MapReduce was the technical term of that day.
M
8:06Michael SlaterGUEST
That was the AI of that day.
D
8:08David O'HaraHOST
Yeah.
4 more episodes mention MapReduce.
Create an account to see the whole feed, search across every transcript, and follow the entities you care about.