Alberto Acerbis, in the second article of his series on Domain-Driven Design and AI, explores why the real risk of AI-driven systems is not the automatic generation of code, but the attribution of the correct meaning to domain concepts.
In this first of two articles on Domain-Driven Design and AI, Alberto Acerbis explores why, in the era of AI-generated code, the primary challenge is no longer producing software, but ensuring that it accurately reflects the intended meaning of the business domain it is meant to represent.
When using LLMs to generate code, the quality of the results depends on the clarity and consistency of your language. Ubiquitous Language becomes a critical framework, acting as the control system for AI-driven development.
In this tenth and final article of the Domain-Driven Design series, Alberto Acerbis explores the role of the Software Architect and how it translates within the world of DDD.
In this ninth article of the series on DDD and evolutionary architectures, Alberto Acerbis explains the difference between Event Storming and Event Streaming—two concepts that may seem similar at first glance.
In the eighth chapter of his Domain-Driven Design series, Alberto Acerbis explores the topic of architectural sustainability and explains why it’s about much more than just code.
In this seventh article in the series on DDD, microservices, and software architectures, Alberto Acerbis explores the concept of antifragility as it applies to agile practices and architectural decisions.
In the sixth article of the series on Domain-Driven Design, Alberto Acerbis discusses the importance of Event-Driven architectures and their key features.
In this fifth article of the series on DDD, microservices, and evolutionary architectures, Alberto Acerbis presents some of the most important tactical patterns and explains why Domain Events should not be shared.
Third article on Domain-Driven Design (DDD), microservices and evolutionary architectures. Alberto Acerbis discusses modular architecture, the meaning of “module,” and how it aligns with DDD strategic patterns.
In this second article on Domain-Driven Design (DDD), microservices and evolutionary architectures, Alberto Acerbis explores the distinction between the problem space and the solution space, highlighting how this separation influences software design.
In this first article exploring the world of Domain-Driven Design (DDD), microservices and evolutionary architectures, Alberto Acerbis offers an overview of the importance of architecture, domain understanding, and best practices that can help design adaptive and effective software systems.