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.
Welcome to dave.dev
I'm David Gee and this is my personal site.
On this site, you can read both new and ported blogs from ipengineer.net and arsonistgopher.com.
Expect systems engineering, control systems, network engineering, network functions (NFC/SFC), software defined and service oriented networking and software development in Python, Go and Rust.
Latest posts from ipengineer.net, arsonistgopher.com and dave.dev
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.
Network engineers for the last twenty years have created networks from composable logical constructs, which result in a network of some structure.
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.