When services don't compose, it's not a bug—it's a mathematical impossibility. Part 4 of applying category theory to Solutions Architecture, where we develop a diagnostic framework for integration failures.
A personal celebration of a decade with the AWS Well-Architected Framework—from reader to contributor—and a philosophical exploration of why it matters as a sociotechnical artifact.
A system is completely characterized by how other systems interact with it. Part 3 of applying category theory to Solutions Architecture—the deepest insight in category theory, made practical.
How Claude Code found 21 improvements in react-lite-youtube-embed: critical bugs, performance wins, and SLSA Level 3 security. A real open source case study
A monolith and microservices can be mathematically equivalent. Part 7 of applying category theory to Solutions Architecture—understanding when radically different implementations are categorically identical.
Stop designing services. Start designing contracts. Part 2 of applying category theory to Solutions Architecture—where we learn that the arrows, not the boxes, are the architecture.
Designing Data-Intensive Applications
Martin Kleppmann
Anna Kariênina
Liev Tolstói
Structure and Interpretation of Computer Programs
Harold Abelson, Gerald Jay Sussman and, Julie Sussman
Fundamentals of Software Architecture
Mark Richards and Neal Ford
Conceptual Mathematics: A First Introduction to Categories
F. W. Lawvere and Stephen H. Schanuel
Links are Amazon affiliate links.
