[deleted]
Talk to a lawyer asap.
Espresso – Google’s peering edge architecture
21–30 of 105 posts
Re: Espresso – Google’s peering edge architecture
#22Re: Espresso – Google’s peering edge architecture
#23I 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 for network-to-network interfaces to provide settlement free peering to major ISPs). The internet is physically built out of a great deal of equipment at layer 1.
In the case of Google, you need to have a team of people who care about things like cost-effectively building intra-datacenter 100GbE layer 2 connections between Google, and large content sinks (eyeball) ISPs such as Charter/TWTC or similar.
Hand waving around and saying "we've built some new software to improve how we efficiently deliver BGP sessions to edge peers" is cool and all, but don't mistake it for some radical change. It is all still built on top of things like 2 megawatt diesel generators, massive battery plants, DWDM line terminals, dark fiber, etc.
Re: Espresso – Google’s peering edge architecture
#24[deleted]
Re: Espresso – Google’s peering edge architecture
#25Two Google products named Espresso? That won't be confusing at all.
Re: Espresso – Google’s peering edge architecture
#26Re: Espresso – Google’s peering edge architecture
#27Re: Espresso – Google’s peering edge architecture
#28[deleted]
Everything you have ever done or ever will do infringes dozens of BS patents. Get back to work.
Re: Espresso – Google’s peering edge architecture
#29Earlier quoted context omitted.
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.
"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. "
"There are only two hard problems in CS : 1. Naming things. 2. Cache invalidation. 3. Off-by-one errors"
Re: Espresso – Google’s peering edge architecture
#30The 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.
For some reason they didn't actually link to the talk, which I haven't watched, but presumably actually tries to start answering those questions.
Quick search is showing the 2015 keynote that Amin gave, haven't found the 2017 one yet...
[1] - 2015 ONS Keynote https://www.youtube.com/watch?v=FaAZAII2x0w