Software Architecture

Una crónica del Domain-Driven Design desde el modelo anémico de los noventa hasta la práctica contemporánea, con manual y catálogo de cuarenta fichas. Para programadores que quieren aplicar DDD con criterio, no por inercia.

AI writes code faster than you can review it. This book gives you the gates: automated guardrails that catch bugs, enforce standards, and verify behavior before bad code reaches production. Stop being the last line of defense. Build the gates that catch the slop first, so you design and verify instead of proofread.

This book is not just another introduction to Domain-Driven Design (DDD). It explores real-world design problems, challenges conventional approaches, introduces new ideas by providing practical guidelines on three levels of abstraction, which the author calls "Clean Backend Application", "Clean Aggregates" and "Clean Domain-Driven Code". The former is the overarching concept, whilst the other two are essential and obligatory building blocks. Together, they form a specialised, systematic approach to the professional software engineering of backend applications. The book is packed with detailed diagrams and code examples. Along the way, readers gain practical guidelines and design insights that help them confidently apply these concepts in their own software projects.

How to put AI agents in production without ending up in the news. A field guide to bounded AI autonomy, MCP security, and AgentSecOps.

The chapter that grew into its own book: existential and universal restrictions, the correct VegetarianPizza pattern, and how OWL restrictions become EKA governance.

Denne bog er skrevet til dig der vil bygge professionel C#-software — ikke bare kode der kompilerer, men kode der kan vedligeholdes, testes, skaleres, og forklares for andre.

Most data modelling books teach you the craft. This one teaches you the reality. Seven chapters of honest, practical guidance from real project experience — covering conceptual modelling, governance, enterprise challenges, and the human side of data work that nobody else writes about.

Stop being a 'Syntax Coder' and start becoming a 'Diagnostic Architect' by mastering the hidden mental models of software failure. This book teaches you how to own every logical branch of your system and eliminate bugs before they even happen. Stop guessing and start diagnosing.

If you've ever wondered what the quantum computing stack actually looks like from top to bottom, this is the book.

Clean, Hexagonal, Onion—one dependency rule, three names. Walk a runnable multi-module SaaS billing service in Scala 3 and ZIO: a pure domain ring, ports and use cases in the middle, PostgreSQL + Flyway + JDBC and a thin HTTP shell on the outside—with full source in the PDF, not truncated snippets. See how ZLayer at the composition root keeps one repository for the whole graph, how webhook idempotency stays on the right side of the boundary, and how munit and zio-test (plus optional Docker) prove the architecture you intend to defend in code review.

CRUD erases the story your system lived through; event sourcing keeps it. Build an account aggregate in Scala 3 and ZIO: past-tense events, a pure applyEvent fold, decide for invariants and idempotency, then wire an append-only PostgreSQL journal, transactions, and a balance projection—and trace one account from HTTP command to read model. When the log must leave the database, follow the same events through transactional outbox, Kafka, and at-least-once consumers without pretending you have magic consistency. For architects and implementers who want decision-grade ES + CQRS, not a toy demo.

No distributed transaction spans your whole business process—so you design steps and compensations instead. In Scala 3 and ZIO, build a full order-placement saga from domain types and service algebras to orchestration and event-driven choreography, with tests that prove compensations fire when things break. Then see what it takes to move the same design toward production: outbox, idempotency, persistence, and how to choose between central coordination and decentralized reactions.

A 1986 text adventure game written inside the Cray I/O Subsystem turns out to be architecturally isomorphic to modern transformer design. This capstone volume uses the playable game and its assembly language source as a case study in constraint-based design, including the bare metal thinking we stopped teaching around 1995.

What was so unusual and special about Cray Research? We accomplished, repeatedly, what nobody else on the planet was able to match. High-Performance Computing is not merely parallelism and large-scale systems. That is the public-facing decoy version.

Build modern, production-ready Android apps with Jetpack Compose using real-world patterns, scalable UI architecture, and professional workflows. This book goes beyond basics to show you exactly how to design, structure, and optimize apps that perform in real development environments. Perfect for developers ready to turn Compose knowledge into polished, portfolio-ready applications.