Pullbacks and Pushouts: Integration Points That Don't Lie
When two services need to agree on something, you need a pullback. When two sources need to merge, you need a pushout. Part 9 of applying category theory to Solutions Architecture.
Cloud, Code & Everything Else
Builder • Startup Co-Founder • TEDx Speaker • Science Fiction Author • Proudly Autistic
AWS Well-Architected
Serverless
TypeScript
Cloud Architecture
This digital garden is bilingual, with posts in en English and pt-br Brazilian Portuguese. Opinions are my own.
Latest Posts
-
-
We Replaced the Build Layer, Not the Runtime
Guillermo Rauch says everyone is now a programmer. Anyone can now build software by writing or speaking — but building something that runs is not the same as understanding why it runs. AI replaced the layer where we author programs, not the runtime they execute on, and the runtime still has to be understood by someone.
-
Products and Coproducts: The Algebra of Service Composition
API Gateways are products. Event routers are coproducts. Part 8 of applying category theory to Solutions Architecture—the universal patterns for combining and decomposing services.
Favorite Books
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.
