On: Espresso – Google’s peering edge architecture

[grkvlt]

I'm sure he means something to do with caches; I had it on the tip of my tongue a moment ago, but the doorbell rang.

[andrewstuart2 → grkvlt]

Surely this is what he meant. Since edge peering/CDN is fundamentally caching (last I checked). It can't be off-by-one, and there are only 2 hard problems in CS, so there you have it.

[bitwiseand → grkvlt]

"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. "

[coderholic → bitwiseand]

"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. 3. Off-by-one errors"

[xapata → bitwiseand]

Only you got the order wrong. One of those distributed systems problems.

[jenscow → grkvlt]

I thought he meant IE support.

[spartanatreyu → grkvlt]

He means naming things

[jamescostian → grkvlt]

I'm pretty sure a lack of coffee is the real issue at hand. Google made more architecture to give peers an edge via two different Espresso shots to test