Espresso – Google’s peering edge architecture
1–10 of 105 posts
Re: Espresso – Google’s peering edge architecture
#2The official Android testing framework from Google is also named Espresso. Are we running into a classic hard computer science problem?
Re: Espresso – Google’s peering edge architecture
#3The official Android testing framework from Google is also named Espresso. Are we running into a classic hard computer science problem?
Off-by-one errors?
Re: Espresso – Google’s peering edge architecture
#4Damn, for a moment there I was hoping that Google made some sort of really cool espresso machine. Perhaps with Alexa built-in.
Re: Espresso – Google’s peering edge architecture
#5Re: Espresso – Google’s peering edge architecture
#6The 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.”
Re: Espresso – Google’s peering edge architecture
#7I 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
Re: Espresso – Google’s peering edge architecture
#8Re: Espresso – Google’s peering edge architecture
#9Can someone with more expertise summarize how this differs from commercial SDN solutions like: Cisco ACI, Juniper Contrail etc.?