You Might Just be a Functional Programmer Now
summary
Argues Kubernetes maps to functional principles: controllers run many independent reconciliation loops that act like an interpreter, container images behave like immutable stack frames, and declarative manifests let the control plane optimize execution. Mentions Cloud Foundry, BOSH, PKS, Helm and Harbor, plus Kafka/event-sourcing parallels. Cites a concrete code example (3,000 → 1,500 → 500 LOC) and an operational practice where Wells Fargo repaves hosts every three days to remove undetected malware, demonstrating the approach works.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 1:30Defining programming models
- 6:08Imperative vs. functional code
- 14:06Reasoning with models
- 17:05Functional systems programming
- 23:18Immutable infrastructure
- 30:24Ephemeral containers
- 33:50Sidecars and conclusion
related talks
32mFunctional Programming for (Dev)Operations and Infrastructure
44mFunctional Programming You Already Know
31mBuilding a Sustainable CodeBase with FP
01h 06mThe Joy of Functional Programming
49m“Applying functional programming in code design"
36mConcrete Functional Programming
57mThe Fun of Functional Programming Panel
54mQ & A Session With Functional Conf Speakers
