7 ms·
I really wanted to understand this article. I tried wikipediaing and googling some of the things I didn't really get (Jupiter is a thing... ok and Andromeda.. r
by komali2 9y ago
I really wanted to understand this article. I tried wikipediaing and googling some of the things I didn't really get (Jupiter is a thing... ok and Andromeda.. riiiight). Then I got to the chart "Conceptually, here is how Espresso plugs into the Google networking stack:", which was totally unparseable by me. All the green things look the same, but one of them is the thing this article is about (Espresso, right?), and Google somehow is represented by a vague dark-grey blob... I just don't get it.
Can anybody help? Am I simply not technically competent enough to consume this article yet?
- trafficlight 9y agoI really hate the naming trend over the past 10-15 years of using common words for projects. I can't really search for Espresso, or Jupiter, or Andromeda without additional qualifiers that I may not know yet.
- komali2 9y agoHeh, that for me culminated when windows released a ubuntu subsystem. The names in order of popularity when it was originally announced (now they push for WSL) 1. Bash for Ubuntu on Windows 2. Windows Bash Shell 3. Windows Subsystem for Linux (WSL) Trying googling WSL - it's world surf league. Windows Bash Shell is impossible, so is Bash for Ubuntu on Windows. It's getting better as more and more articles are being written, but god almighty. I wouldn't be surprised if google is lending a helping hand with searches for WSL stuff.
- Swizec 9y agoIt's a filter bubble issue. When I first started Ruby, it had been popular for 10+ years already. Many articles. Despite that, it was still impossible to search for. Look for Ruby, get gemstones. Look for gem, get even more gemstones. Eventually Google figured it out and now it's almost impossible to search for gemstones. If I search for gem almost all search results are about Ruby things. Same when searching for Ruby. Even "rails" now returns almost only Ruby on Rails stuff.
- komali2 9y agoHave you tried searching when logged out of google? I'd imagine a rail worker searching lots of train stuff would generally get the right results when they searched on their account. But yea, worth bearing in mind when naming stuff.
- deleted 9y ago[deleted]
- true_religion 9y agoPerhaps, but under incognito I still get Ruby on rails if I search for "rails". I do get train info if I search for "rail".
- flavor8 9y agoTry the same searches from an incognito window. It could just be that Google learned what Ruby you are searching for.
- vidarh 9y agoI just did: 1. Download Ruby 2. Ruby entry on wikipedia (about the gemstone) All the rest on the first page are about the programming language in some way or the other (Rails, various books, various tutorial resources, Stackoverflow, trending on Github)
- milcron 9y agoAnd the 3rd name is backwards. It ought to be called 'Linux Subsystem for Windows'.
- SpaceManNabs 9y agoTHAT IS IT! I was wondering why the name always felt funky. Although the name they have now is technically correct if you ignore standard noun to adjective conventions.
- pavement 9y ago...or it's missing an apostrophe. a. Windows' Subsystem for Linux b. Window's Subsystem for Linux Each option has its own sort of context.
- bdowling 9y agoIf you're making it a possessive using an apostrophe, then it should be "Windows's Subsystem for Linux" because Windows is singular in that context.
- IncRnd 9y agoThat's not the entire story, unfortunately. There are other rules. For example, Windows might be considered a family name, as there are several Windows Operating Systems. Also, this is a technical name, and technical writing often follows different rules, specifically in cases such as this. For the possessive form of Windows I would look at the Microsoft Manual of Style, which for me is the fourth edition. Page 184: Possessive Nouns -------------- Do not use the possessive form of Microsoft. Do not use the possessive form of other company names unless you have no other choice. And do not use the possessive form of a product, service, or feature name. You can use these names as adjectives, or you can use an of construction instead. Microsoft style: the Windows interface Microsoft products, services, and technologies Word templates --------------
- 9y ago
- userbinator 9y agoIndeed, it would've been far better if they called it WinBuntu Bash or some other similarly distinctive name. ...then again, WINE isn't exactly unique either.
- skrebbel 9y agoThe internal name is lxss. I'm sad they didnt make that the default because it's very googlable. That said WSL tends to work if you pair it with whatever your issue is. IMO the most ridiculous name in this whole story is their github repo, Microsoft/BashOnWindows. I mean, bash has worked fine on Windows for decades, and it doesn't require an entire subsystem at all :-) WSL isn't half bad compared to that.
- AznHisoka 9y agoAlso when did EmcaScript conveniently became ES? when i see someone mention ES6, I think its elasticserch but its not
- TeMPOraL 9y agoI hate it too. Especially if they take something with a somewhat awesome name. It waters the meaning down. My go-to example is Terraform, a glorified configuration manager that has absolutely nothing to do with the process of terraforming.
- adrianratnapala 9y agoTo me it seems a return to the an older tradition, of names being names rather than descriptions (which inevitably fail to describe). Using common words for names is also ancient and inevitable. In the modern age there is a practical argument against it -- as made up nonsense is more googlable. But people making up names don't really care about that in any visceral way.
- captainlego 9y agoWhile your original point is valid, I did get decent results with "Google Espresso", "Google Jupiter Network", and "Google Andromeda Network". Though, in today's world, your Google results may look vastly different from mine.
- windowsworkstoo 9y agoI cant really help because Im not great at explaining things, but for some fundamentals, you need to understand BGP and label switching (MPLS). The cleverness here is that they effectively turned their routers in label switchers, with the label traffic is sent to determined by backend infra, not the router itself. They still have to run this over BGP of course, as thats how the internet works but it is an interesting approach for optimizing return traffic routes. Edit: espresso is the name of the stack they use to make the label switch decision, its not a protocol or industry standard
- 3131s 9y agoI understand as much as is to be expected after looking at someone else's (Google's) huge software stack in an area that is not my specialization (networking). My only tip is to not actually worry about grasping everything at first and just start to build up lists of facts and associations (e.g. "Espresso is a networking stack to do routing over the public Internet", "Espresso pulls the routing intelligence outside of individual routers into a server pool"). With time and after studying more of the conceptual background, everything starts to make sense typically. There are definitely some Googlisms or something being thrown around though. Can anyone tell me what a "hypercaler" is?
- rbobby 9y ago> "hypercaler" Probably a typo for https://www.hyperscalers.com/ https://www.hyperscalers.com/
- erentz 9y agoIt's extremely high level and vague presumably by intention. If you don't have a grounding in networking, BGP, traffic engineering (MPLS, SR, related concepts), you won't be able to make out much about it. If you do, you'll just infer that they're doing a form of "egress peer engineering". On top of that it sounds like they're potentially using whitebox switches at the edge and terminating BGP peering sessions on servers which are programming the forwarding state on these white boxes.
- FrozenVoid 9y agoI have little to nothing expirience in BGP and routing. It seems they cloudified the routing layer by making their machines part of some 'abstract router cloud' that can be reconfigured at will(centrally).
- mandarg 9y agoHere's my attempt at an explanation, after reading the article. Most companies' networks have edge routers (which sit at the points where they connect to other networks) and core routers (which manage the flow of traffic inside the network. All these routers basically use a standard protocol called BGP (Border Gateway Protocol) which is defined by RFC 4271. However, BGP was still designed from the view of individual machines making routing decisions and announcing routes to each other that collectively make up the whole Internet. This helps the Internet as a whole be quite resilient – if one network goes down, there are still ways to route traffic through to other networks. Also, since the protocol is standard, you can swap out one vendor's gear for another at will (in theory anyway) as long as you know how to configure it correctly. But this leads to some inefficiency – for instance, it is very hard to say that a path with fewer hops will lead to lower latency. What Google seems to have done is to make their edge routers into one single "intelligent" network, where the edge routers don't make routing decisions on their own, but feed their data into a central server. This central server can then say stuff like "My peering router in NYC seems to be under heavy load, let me redirect some of my traffic to NYC destinations through the NJ datacenter instead", or something to that effect; while still doing the correct BGP announcements from the point of view of Level3 or whoever is peering. In short, they built their internal network from the ground up since they are so big they can afford to build custom routing gear instead of using the standard off-the-shelf, standardized setup that a small or medium-sized company uses. The network consisting of their custom edge routers (all the green blobs) together is called Espresso and represented by a light grey circle.
- Animats 9y ago"Central server" for routing. Uh oh. AT&T used to try to avoid centralization, but ended up with routing controlled from Bedminster, NJ.[1] An interesting comment from AT&T's NOC tour guide is that load doesn't vary much any more. AT&T used to have holiday calling surges and such, but now, in an always-on world, overall load is relatively steady. [1] http://fortune.com/att-global-network-operations-center/ http://fortune.com/att-global-network-operations-center/
- runeks 9y ago
- bogomipz 9y agoIt's a pretty terribly written article and that info graphic is also not very helpful. This article is like two people discussing "inside baseball." The essence of the article is the evolution of Google's SDN(software defined networking) architecture. They have added SDN to their edge whereas previously SDN existed mostly in their Core it sounds like. The Edge SDN architecture being "Espresso" and the Core SDN architecture being "Jupiter." There is also some fishing about what exactly is Google's network hardware that runs all this. The following article is far more brief but far more informative in my opinion: https://www.sdxcentral.com/articles/news/google-brings-sdn-public-internet/2017/04/ https://www.sdxcentral.com/articles/news/google-brings-sdn-p... This is a white paper about Jupiter mentioned in the article and infographic: https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43837.pdf https://static.googleusercontent.com/media/research.google.c... And there's some good resources here for just learning about SDN here: https://www.opennetworking.org/sdn-resources/sdn-definition https://www.opennetworking.org/sdn-resources/sdn-definition
- hueving 9y agoGoogle produces notoriously opaque and high-level articles with regard to its networking systems. You are not meant to get much meaning out of them. Instead you should stand back in awe at the amazing things they are doing. Nearly every Google paper about Google networks in SIGCOMM is utter trash that would have been rejected in an instant due to lack of novel details if it had come from anyone else. They just brag about scale, utilization, and resiliency without actually giving anything back to the academic community. Note: This does not apply to all Google papers (e.g. spanner and other DB ones are pretty good). Their networking publications seem to be crippled by either IP concerns or poor academic writers.
- valas 9y agoDisclaimer: I worked on this technology. I agree, article could be improved. In a nutshell, Espresso system allows (logically) centralized, fine-grained control of how bits leave Google's network. Specifically, each server has a tailored (for that server) routing table that allows the server to select a specific port on a specific peering router for a given packet to exit to. The routing tables are updated very often and fast (e.g. to remove references to links that went down). This makes it very easy to move bits around. You want to shift 42.2% of link X traffic to link Y? Just update some routing tables in end hosts. It also allows for different applications to the same destination to use different exit links (e.g. low latency - exit somewhere close, high bandwidth - exit where we have bandwidth). Bonus benefit: router can be simpler, it doesn't need to do any routing anymore, it just needs to follow instructions on each packet on which port to forward the packet to. Does it make it more clear? Ask me anything.