TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Espresso – Google’s peering edge architecture

327 点作者 vgt大约 8 年前

17 条评论

itchyjunk大约 8 年前
&quot;We defined and employed SDN principles to build Jupiter, a datacenter interconnect capable of supporting more than 100,000 servers and 1 Pb&#x2F;s of total bandwidth to host our services.&quot;<p>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.<p>&quot;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.&quot; Is this implying they are using Machine Learning to improve their own version of content delivery network?
评论 #14039229 未加载
mmaunder大约 8 年前
&quot;Google has one of the largest peering surfaces in the world, exchanging data with Internet Service Providers (ISPs) at 70 metros and generating more than 25 percent of all Internet traffic. &quot;<p>Wow.
评论 #14039437 未加载
Apocryphon大约 8 年前
The official Android testing framework from Google is also named Espresso. Are we running into a classic hard computer science problem?
评论 #14038086 未加载
评论 #14040740 未加载
评论 #14041147 未加载
smaili大约 8 年前
The essence of what Espresso is begins towards the end of the post:<p><i>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.</i><p><i>Second, we separate the logic and control of traffic management from the confines of individual router “boxes.”</i>
评论 #14038372 未加载
dkhenry大约 8 年前
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
评论 #14038219 未加载
评论 #14038441 未加载
评论 #14038306 未加载
hueving大约 8 年前
These presentations from Google are pretty irritating at these conferences. If you&#x27;re familiar with the SDN field (as most ONS attendees would be), this presentation is essentially nothing but bragging about the scale at which they operate.<p>There is no useful information in here to advance the state of the art, no new ideas, no publicly available implementations (closed or open source). It&#x27;s just a very high-level architectural view of a large network given by people who are incentivized to present it in the most favorable light. And due to the lack of any concrete details, it&#x27;s free from critical analysis.<p>&gt;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.”<p>The first has been done before at many levels of the network:<p>* BGP anycast<p>* DNS responses based on querier<p>* Done in load balancer<p>* IGP protocols to handle traffic internally while taking into account link congestion<p>I assume their framework gives them much nicer primitives to work with than the above, which would be an advancement in the field if we could actually see an API or something.<p>The second is very far from &quot;innovation&quot;. This is the essence of SDN and this has been the hottest thing since sliced bread in the networking world since 2008 at a minimum [1] and even earlier if you look at things like the Aruba wireless controller.<p>1. <a href="http:&#x2F;&#x2F;archive.openflow.org&#x2F;documents&#x2F;openflow-wp-latest.pdf" rel="nofollow">http:&#x2F;&#x2F;archive.openflow.org&#x2F;documents&#x2F;openflow-wp-latest.pdf</a>
评论 #14042410 未加载
评论 #14041803 未加载
评论 #14049979 未加载
评论 #14051129 未加载
filereaper大约 8 年前
Yup, this is the kind of thing you get when you put in $30B into infrastructure.<p><a href="https:&#x2F;&#x2F;youtu.be&#x2F;j_K1YoMHpbk?t=7472" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;j_K1YoMHpbk?t=7472</a>
NTDF9大约 8 年前
Can someone with more expertise summarize how this differs from commercial SDN solutions like: Cisco ACI, Juniper Contrail etc.?
评论 #14038235 未加载
apanda大约 8 年前
This vision seems very similar to the 2011 talk by Scott Shenker: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=YHeyuD89n1Y" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=YHeyuD89n1Y</a>
评论 #14077082 未加载
danm07大约 8 年前
Distracting aside: It&#x27;s amusing that languages use so many references from the coffee industry. I wonder how long it will take to fill a Starbucks menu.
piyushpr134大约 8 年前
One biggest takeaway from this is that they can have multiple machines for the same IP address. That is just awesome and also explains how they have probably managed to scale up services 8.8.8.8 without needing to use load balancers.
评论 #14040548 未加载
soVeryTired大约 8 年前
What does &quot;peering edge&quot; mean? A google search only brings up this article.
评论 #14040752 未加载
评论 #14040744 未加载
KaoruAoiShiho大约 8 年前
This is pretty impressive.
s73ver大约 8 年前
Two Google products named Espresso? That won&#x27;t be confusing at all.
评论 #14039036 未加载
评论 #14040869 未加载
评论 #14040748 未加载
neduma大约 8 年前
tl;dr?
sebnap大约 8 年前
Wow. Isn&#x27;t this a trojan horse? People start to use it because of it&#x27;s convenience and then it will spread and spread and spread. I mean what&#x27;s up when google will run more or less everything?
Bud大约 8 年前
Damn, for a moment there I was hoping that Google made some sort of really cool espresso machine. Perhaps with Alexa built-in.
评论 #14038805 未加载