Not Storing State in the Network OpenFlow (OF) adoption failed due to scalability of forwarding tables on ASICS, not so great controllers, lack of applications and a non-existent community.

This is part one of a series of posts on Application Composition within Network Service Meshes, otherwise known as Service Function Chaining, but at L7 and not L3/L4.

From the days of old, setting fire to a large torch would signal to a neighbouring town something was going on.

Dave Cheyney, Wizard extraordinaire posted a challenge on clarity for multi-argument functions.

Network engineers for the last twenty years have created networks from composable logical constructs, which result in a network of some structure.

For the last five or six years, I’ve not really done any networking and have focussed on software, automation and the mechanisation of processes so that they may be manifested as network driving workflows.

In this post I’ll explore replacing the heart of a network operating system’s configuration mechanism with the software developers take on version control.

Week of 24th June 2019 was interesting. We had #ferrogate which made a lot of network engineers very unhappy and also an ongoing social media thread on code comments.

Workflows vary from seriously simple to notoriously complex and as humans, we might not even consciously observe the subtleties of what a workflow comprises of.