Introduction
Throughout my career I’ve applied and tested solutions against SOLID Principles. These principles were conceived to make object-oriented designs more understandable, flexible, and maintainable. The following examples illustrate each principle:
Incidents often result from contributing factors as opposed to a singular root cause. As a result, causal diagrams can be an effective tool for illustrating incidents.
Someone recently asked me to help diagnose a mysterious delay on a globally deployed Elixir service.
What happens when routing changes for a stateful network protocol and unexpectedly arrives at a device without a session?
I’ve recently discovered the Docker network macvlan driver.
A macvlan driver creates virtual network interfaces, each with its own unique MAC address, that can be configured to communicate with other devices on a network. These virtual interfaces behave like separate physical network interfaces and can be assigned their own IP addresses and network settings.
This post is dedicated to how I would shape a “consulting” style Site Reliability Engineering (SRE) engagement.
I recently broke my apex domain HTTPS redirect to my subdomain.
These are some notes taken while deploying a Digital Living Network Alliance (DLNA) to Kubernetes. DLNA is derived from Universal Plug and Play (UPnP) specifically for media interoperability. DLNA services are advertised and discovered via Simple Service Discovery Protocol (SSDP).
I’ve rolled my own Dynamic DNS Operator with Kubernetes CronJob, kubectl, and External DNS. I’m going to try capture the solution in a Google Design Document.
For the love of proxies - please read this.