Espresso – Google’s peering edge architecture

Re:Espresso – Google’s peering edge architecture by Apocryphon on Tuesday April 04, 2017 @07:02PM (#14038079)

The official Android testing framework from Google is also named Espresso. Are we running into a classic hard computer science problem?

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by Y_Y on Tuesday April 04, 2017 @07:03PM (#14038086)

Off-by-one errors?

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by grkvlt on Tuesday April 04, 2017 @07:05PM (#14038110)

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.

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by andrewstuart2 on Tuesday April 04, 2017 @07:40PM (#14038315)

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.

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by bitwiseand on Tuesday April 04, 2017 @08:16PM (#14038554)

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

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by coderholic on Tuesday April 04, 2017 @08:26PM (#14038601)

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

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by xapata on Tuesday April 04, 2017 @11:51PM (#14039518)

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

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by jenscow on Tuesday April 04, 2017 @07:49PM (#14038381)

I thought he meant IE support.

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by spartanatreyu on Tuesday April 04, 2017 @07:20PM (#14038203)

He means naming things

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by jamescostian on Tuesday April 04, 2017 @08:38PM (#14038661)

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

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by IncRnd on Tuesday April 04, 2017 @07:23PM (#14038216)

Not if they developed using Espresso CSS editor that just had v3 released on March 30th.

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by knorker on Wednesday April 05, 2017 @05:03AM (#14040740)

There are two whole things at Google called "Espresso"?

Oh no. I bet this reuse of a name has gone unnoticed internally until now.

[ Parent | on HN ]

Re:Espresso – Google’s peering edge architecture by _pmf_ on Wednesday April 05, 2017 @06:53AM (#14041147)

> The official Android testing framework from Google is also named Espresso.

This just shows that Android is treated as the ugly step child even within Google (not that this is not already obvious given the state of the Android API).

[ Parent | on HN ]