Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Espresso – Google’s peering edge architecture

blog.google

Post reply on HN
Print view View original

31–40 of 105 posts

Re: Espresso – Google’s peering edge architecture

#31

Post by [deleted] »

EE84M3i wrote: post #20
smaili wrote: post #6

The essence of what Espresso is begins towards the end of the post: Espresso delivers two key pieces of innovation. First, it allows us to dynamically choose from where to serve individual users based on measurements of how end-to-end network connections are performing in real time. Second, we separate the logic and control of traffic management from the confines of individual router “boxes.”

I found this article confusing. It doesn't really say anything about what "Espresso" actually does, let alone how it does it.

[deleted]

Re: Espresso – Google’s peering edge architecture

#32

Post by jamescostian »

grkvlt wrote: post #5
Y_Y wrote: post #3

Earlier quoted context omitted.

Off-by-one errors?

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.

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

Re: Espresso – Google’s peering edge architecture

#33

Post by itchyjunk »

"We defined and employed SDN principles to build Jupiter, a datacenter interconnect capable of supporting more than 100,000 servers and 1 Pb/s of total bandwidth to host our services."

This type of scales boggle my mind. Though I have found I can no longer keep up with all the terminologies popping up every day. Posts like these are my only connection to learning the massive scaling of things to make the modern networks work.

"We leverage our large-scale computing infrastructure and signals from the application itself to learn how individual flows are performing, as determined by the end user’s perception of quality." Is this implying they are using Machine Learning to improve their own version of content delivery network?

Re: Espresso – Google’s peering edge architecture

#38

Post by lnanek2 »

s73ver wrote: post #25

Two Google products named Espresso? That won't be confusing at all.

Yeah, was annoying thinking this article was relevant to my every day life as an Android developer until I looked farther. Is it so tough for Google to Google a name before they pick it? Geez.

Re: Espresso – Google’s peering edge architecture

#40

Post by nickpsecurity »

walrus01 wrote: post #23
dkhenry wrote: post #7

I think with platforms like this it is now safe to say that the systems and services Google is deploying are no longer in the same category as classical networked systems. This is as foreign a concept from traditional networking and the seven layer OSI model as non von Neumann computing is from von neumann computing

> This is as foreign a concept from traditional networking and the seven layer OSI model cough cough what? One of the major challenges for a CDN is predicated upon OSI layers 1 and 2: You need to establish POPs with routers and caching servers geographically distributed near major IX points (L2 peering fabrics, and crucial buildings that host the same IX points, where you can run intra-building fiber crossconnects fo…

In other words, it's built on hundreds of millions to billions of dollars of typical, boring stuff on the bottom that allows all the cool stuff to work as well as it does.
Post reply on HN