Best of Domain-Driven Design — August 2025

1. 1
   Article

   Jobs·41w

   Domain Driven Design: Key Concepts and Practical Approach

   Domain Driven Design is not about creating domain folders but about modeling code around business responsibilities with clear subdomain boundaries. Each subdomain should handle its own responsibilities and communicate through well-defined interfaces, creating parent-child relationships where domains collaborate through contracts rather than direct dependencies. The approach emphasizes balancing abstraction with practicality, distinguishing between library code (heavily abstracted for reuse) and domain code (tied to specific business contexts).

   103

   2
2. 2
   Article

   ByteByteGo·40w

   EP176: How Does SSO Work?

   Single Sign-On (SSO) enables users to access multiple applications with one login through Identity Providers and Service Providers. The newsletter covers API design best practices including clear naming, idempotency, pagination, and security. Domain-Driven Design concepts are explained including Entities, Value Objects, and Aggregates. Popular AI agent frameworks like LangChain, AutoGen, and CrewAI are compared for building intelligent systems. OpenAI's new open-source GPT-OSS models use Mixture-of-Experts architecture with specialized neural networks for efficient processing.

   26
3. 3
   Article

   Architecture Weekly·39w

   My thoughts on Vertical Slices, CQRS, Semantic Diffusion and other fancy words

   Explores the relationship between Vertical Slice Architecture (VSA) and CQRS, arguing that VSA is essentially CQRS with more prescriptive organizational guidance. Discusses two main approaches to implementing vertical slices: pure self-contained slices versus slices with thin coordination layers. Addresses how semantic diffusion corrupts architectural patterns over time, turning simple concepts like CQRS and VSA into complex, misunderstood implementations with unnecessary constraints. Emphasizes that both patterns work well for simple CRUD systems and can evolve as complexity grows.

   20

   2