This post shares some musings on the matter of the importance of consumable topology in automation.

A requirement came up to extract a schema from a Terraform provider in JSON, which Terraform offers as a native feature as of version 0.

Some thoughts on systems that I describe as natural ones. These systems allow constituent components to behave within confines of wider system rules and don’t care for specifics.

Brace yourself reader. Future me, you may disagree with what’s in here.

Following the Path Welcome to part four of this series. This this final part, we will explore our options for networking a composed application, from a de-composed monolith or set of microservices.

Application De-Composition Applications are ever evolving and so are the architecture patterns:

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.