Practical Simplification
Simplification is a constant theme not only here, and in my talks, but across the network engineering world right now. But what does this mean practically? Looking at a complex network, how do you begin simplifying?
The first option is to abstract, abstract again, and abstract some more. But before diving into deep abstraction, remember that abstraction is both a good and bad thing. Abstraction can reduce the amount of state in a network, and reduce the speed at which that state changes. Abstraction can cover a multitude of sins in the legacy part of the network, but abstractions also leak!!! In fact, all nontrivial abstractions leak. Following this logic through: all non-trivial abstractions leak; the more non-trivial the abstraction, the more it will leak; the more complexity an abstraction is covering, the less trivial the abstraction will be. Hence: the more complexity you are covering with an abstraction, the more it will leak.
Abstraction, then, is only one part of the solution. You must not only abstract, but you must also simplify the underlying bits of the system you are covering with the abstraction. This is a point we often miss.
Which returns us to our original question. The Continue reading
The filing comes less than a year after Fastly’s latest funding round: a $40 million Series F...



Karbon is an on-premises Kubernetes platform that combines storage, networking, observability, and...
Early 5G coverage is spotty, service is limited, signals often drop within hundreds of feet of a...
SDxCentral Weekly Wrap for April 19, 2019: Ericsson's China offices are raided by antitrust...
Priyanka Sharma, director of technical evangelism at the company, said that the expansion of...