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

41–50 of 105 posts

Re: Espresso – Google’s peering edge architecture

#41

Post by sroussey »

itchyjunk wrote: post #33

"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 netwo…

The google network is gold plated, lacks the jitter inherent in the internet at large or inside other competitors' networks. It makes it tempting to ignore some aspects of distributed computing, if only for a moment.

Re: Espresso – Google’s peering edge architecture

#42

Post by felipemnoa »

sroussey wrote: post #41
itchyjunk wrote: post #33

"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 netwo…

The google network is gold plated, lacks the jitter inherent in the internet at large or inside other competitors' networks. It makes it tempting to ignore some aspects of distributed computing, if only for a moment.

Could you expand a bit more on you comment? I feel I'm missing some context. Specifically, what do you mean by gold plated? Why is it tempting to ignore some aspects of distributed computing? I'm missing a lot of context that you are implicitly implying so could you elaborate?

Re: Espresso – Google’s peering edge architecture

#43

Post by jodrellblank »

nickpsecurity wrote: post #40
walrus01 wrote: post #23

Earlier quoted context omitted.

> 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.

that allows all the cool stuff to work as well as it does.

that allows all the advertising to draw in ad spend as well as it does.

Re: Espresso – Google’s peering edge architecture

#44

Post by geeio »

felipemnoa wrote: post #42
sroussey wrote: post #41

Earlier quoted context omitted.

The google network is gold plated, lacks the jitter inherent in the internet at large or inside other competitors' networks. It makes it tempting to ignore some aspects of distributed computing, if only for a moment.

Could you expand a bit more on you comment? I feel I'm missing some context. Specifically, what do you mean by gold plated? Why is it tempting to ignore some aspects of distributed computing? I'm missing a lot of context that you are implicitly implying so could you elaborate?

I assume they are talking about things like the truetime clocks used in spanner, which are not available on commodity hardware

Re: Espresso – Google’s peering edge architecture

#45

Post by jemfinch »

felipemnoa wrote: post #42
sroussey wrote: post #41

Earlier quoted context omitted.

The google network is gold plated, lacks the jitter inherent in the internet at large or inside other competitors' networks. It makes it tempting to ignore some aspects of distributed computing, if only for a moment.

Could you expand a bit more on you comment? I feel I'm missing some context. Specifically, what do you mean by gold plated? Why is it tempting to ignore some aspects of distributed computing? I'm missing a lot of context that you are implicitly implying so could you elaborate?

He's saying that it's so reliable and the throughput is so high that sometimes you have to convince yourself that your computers are halfway across the planet.

Re: Espresso – Google’s peering edge architecture

#47

Post by dalailambda »

felipemnoa wrote: post #42
sroussey wrote: post #41

Earlier quoted context omitted.

The google network is gold plated, lacks the jitter inherent in the internet at large or inside other competitors' networks. It makes it tempting to ignore some aspects of distributed computing, if only for a moment.

Could you expand a bit more on you comment? I feel I'm missing some context. Specifically, what do you mean by gold plated? Why is it tempting to ignore some aspects of distributed computing? I'm missing a lot of context that you are implicitly implying so could you elaborate?

Building distributed systems makes you aware of how unreliable things are at the large scale, e.g. the network. The parent comment implies that Google's network is so fast and reliable that it becomes tempting to ignore best practices and work as if it's a non distributed system.

Re: Espresso – Google’s peering edge architecture

#49

Post by wbl »

geeio wrote: post #44
felipemnoa wrote: post #42

Earlier quoted context omitted.

Could you expand a bit more on you comment? I feel I'm missing some context. Specifically, what do you mean by gold plated? Why is it tempting to ignore some aspects of distributed computing? I'm missing a lot of context that you are implicitly implying so could you elaborate?

I assume they are talking about things like the truetime clocks used in spanner, which are not available on commodity hardware

Depends on commodity. You can just buy GPS slaved rubidium clocks with PTP output.
Post reply on HN