[irq]: techie interrupted


“ What we have seen is that a logically centralized, hierarchical control plane with a peer-to-peer data plane beats full decentralization,” explained Vahdat in his keynote. “All of these flew in the face of conventional wisdom,” he continued, referring to all of those projects above, and added that everyone was shocked back in 2002 that Google would, for instance, build a large-scale storage system like GFS with centralized control. “We are actually pretty confident in the design pattern at this point. We can build a fundamentally more efficient system by prudently leveraging centralization rather than trying to manage things in a peer-to-peer, decentralized manner. „

Google Lifts Veil On “Andromeda” Virtual Networking


Enabling Fast, Dynamic Network Processing with ClickOS, Joao Martins, NEC (by TheLinuxFoundation)


“ Snabb Switch is a toolkit for solving novel problems in networking. If you are building a new packet-processing network appliance then you can use Snabb Switch to get the job done more quickly. „

Home · SnabbCo/snabbswitch Wiki · GitHub



“ VyOS is a community fork of Vyatta, a Linux-based network operating system that provides software-based network routing, firewall, and VPN functionality. „






The Picture You Paint Of The Browser Is That It Has Become Very Complicated With Many Ways To Send And Consume Data (Ajax, DataChannel, WebRTC, WebSocket, SSE). Has The Browser Jumped The Shark Complexity-Wise?

Actually, I would argue that it’s pretty simple once you know the underlying mechanics and use cases for each of the API’s. Take AJAX, SSE, and WebSocket: AJAX is optimized for HTTP request-response, SSE is for server-side streaming over HTTP, and WebSocket is for bi-directional streaming. On the other hand, WebRTC and DataChannel are for P2P communication. Once you know your use case, you can quickly narrow down the list to one or at most two API’s. From there, you need to take a look under the hood of each protocol to understand how it works, and how you should optimize your application code to get the best performance from it. That’s what HPBN is all about.


High Scalability - High Scalability - Interview With Google’s Ilya Grigorik On His New Book: High Performance Browser Networking


“ One of points I made was we have been building networks around the concept of reachability and interoperability for 30-40 years and that networking is hard, mainly because we make it hard. We turn everything on and proceed to turn things off by using QoS, firewalls, VLANs, DPI, load balancers, etc. Then the thought occurred to ask what would happen if we revered this process? What if the network was off by default and we turned it on based around services, workloads and applications? „

Framing Exercise:::What if we Turned the Network Off? | SIWDT



Well-designed architecture has complexity (and state) concentrated at the network edge. The core devices keep minimum state (example: IP subnets), while the edge devices keep session state. In a virtual network case, the hypervisors should know the VM endpoints (MAC addresses, IP addresses, virtual segments) and the physical devices just the hypervisor IP address, not the other way round.

Furthermore, as much state as possible should be stored in low-speed devices using software-based forwarding. It’s pretty simple to store a million flows in software-based Open vSwitch (updating them is a different story) and mission-impossible to store 10.000 5-tuple flows in Trident 2 chipset used by most ToR switches.


50 Shades of Statefulness « ipSpace.net by @ioshints

blog comments powered by Disqus
page 1 of 89 | next »
Tumblr » powered Sid05 » templated Disquss » commented