Skip to main content

Topic

Linux & Networking

Every container, cluster and pipeline eventually resolves to a Linux process holding a file descriptor. When something behaves inexplicably a layer up, the answer is usually here: a permission, a full disk, a port already bound, a process that ignored a signal.

The same applies to networking. Reverse proxies, timeouts and certificates cause a large share of production incidents, and they are far easier to reason about once you have seen how a request actually traverses them.

Articles
3
Answered questions
1