Ryan Peterman

You gave a talk, and I think there's also a paper behind it, of this idea that one size fits all database systems, not optimal.

One size actually fits none.

And that what you really want is database solutions that target specific needs.

What database offerings do you see today that are one size fits all?

GPUs, do they make available some new opportunities to optimize databases?

Can you explain why indexing would be not as effective when there's SIMD?

You mentioned B-trees.

When you first implemented that first version of Ingress,

Did you write all of that by hand?

Because I imagine there's probably not some existing B-tree library or something.

Yeah, we wrote, the original version of Ingress was all written from scratch.

What was the hardest part of that implementation?

And why was that hard?

MapReduce came out at some point in the early 2000s, and it kind of took the data world by storm.

People were really impressed by it.

They thought Google really knows what they're doing.

This is the best thing since sliced bread.

But it seems like when I look at the literature and what you thought at the time, you kind of disagreed heavily.

Why did you disagree so much with MapReduce?

Well, I think...