What could Functional Architecture mean?
summary
Argues that "functional architecture" means deriving an algebra of components that lets designers map and recombine system behaviors; uses the build-systems paper "Build Systems a la Carte" as concrete evidence, formalizing build systems in Haskell types and showing how tasks as Applicative vs Monad yield static (Excel-like) versus dynamic dependencies. Shows a table mapping implementations (make, shake, nix) to type-and-scheduler choices, claims this exposes essential complexity rather than vague "hard to change" labels, and treats Haskell as the analytic tool rather than the final deploy target.
AI-written summary · about
chapters (7)
- 0:00Functional architecture intro
- 1:05Defining software architecture
- 5:21Build systems example
- 9:58Algebra of components
- 12:45Essential versus accidental complexity
- 20:27Language choice impact
- 23:16Q&A
related talks
17mFunctional Architecture is Algebraic Architecture
56mIntroduction to Functional Software Architecture
01h 00mWhy Your Architecture Is Functional and How to Live with It
45mFunctional Programming in the Large - Status and Perspective
49mApproaching Functional Programming Through Hexagonal Architecture
34mPatterns of a pragmatic functional architecture
20mOn the paradigm of functional programming
38mFunctional Programming - The Architecture of Choice