Cloud architecture, serverless computing, and software engineering insights from an AWS Well-Architected team member. Exploring event-driven architectures, domain-driven design, and the intersection of technical excellence with business outcomes. Bilingual content in English and Brazilian Portuguese.
Flexibility vs. governance. Performance vs. cost. Consistency vs. availability. These aren't problems to solve—they're adjunctions to navigate. Part 11 of applying category theory to Solutions Architecture.
Products, pullbacks, and terminal objects are all limits. Coproducts, pushouts, and initial objects are all colimits. Part 10 of applying category theory to Solutions Architecture—the unified theory.
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.
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.
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.
A tradução brasileira de Estrutura e Interpretação de Programas de Computador — Edição JavaScript está completa. Um livro sobre feiticeiros, daemons e a mais antiga das artes humanas: transformar conhecimento em maravilhas.
When you change from one architecture to another, changes must be consistent everywhere. Part 6 of applying category theory to Solutions Architecture—the mathematics of coherent transformation.
Every migration is a functor — a structure - preserving transformation between systems. Part 5 of applying category theory to Solutions Architecture, where we learn when migrations succeed and why they fail.
Uma explicação visual e interativa de como Large Language Models processam texto, desde a tokenização até a geração de respostas. Descubra por que eles 'alucinam' e não são determinísticos.
When services don't work together, it's not random—it's one of four predictable failure modes. A practical guide to diagnosing and fixing integration problems using insights from category theory.
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.
Category theory isn't abstract nonsense—it's the formal language for the problems Solutions Architects already face. Part 1 of a series on applying mathematical foundations to real architectural challenges.
Announcing my MBA thesis research: applying category theory, sheaf cohomology, and cybernetics to understand why some open source projects thrive while others collapse. Can we predict governance crises before they happen?
From Bartosz Milewski's Haskell-centric approach to something tailored for the JS/TS ecosystem. Exploring adjunctions, monads, and why Promise.then() is actually category theory in disguise.
AWS CDK (Cloud Development Kit) is an open source framework to provision infrastructure in the Cloud by writing code in Python, TypeScript, JavaScript, .NET, Java