# DDD Published articles for DDD. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Fragments: June 16 DevFeed: [Fragments: June 16]() Original publisher: [Read original article]() Author: Martin Fowler (martin@martinfowler.com) Published: 2026-06-16T12:44:00Z Content type: article Language: en Sources: [Martin Fowler]() Topics: [Domain-driven design (DDD)](), [Large Language Model](), [context window](), [Programming]() Tags: [conference](), [context-window](), [ddd](), [event](), [llm](), [programming]() ### AI overview This article fragment discusses how large language models are changing the experience of programming and argues that Domain-Driven Design may remain useful or become more important. It also highlights managing an LLM context window and using distinct conversation registers for exploring, brainstorming, deciding, and implementing. ### Source excerpt "Prag Dave" Thomas (co-author of the outstanding "Pragmatic Programmer") has loved programming since he was young. Programming was how I could express myself. I wasn't an artist. When I sing, dogs howl. When I draw, friends say, "Very nice. What is it?" I didn't connect particularly well with people, even though I wanted to. And yet, when I wrote my first program, I discovered a medium which let me convert thought into action. All the ideas that were bottled up behind a wall of frustration suddenly had an outlet. The LLM revolution worried him. Would they remove all that fun stuff? Happily he found it was the opposite. Like Kent Beck and others have told me, programming with LLMs is more fun than ever. His post lists reasons why: removing drudgery, speeding up feedback loops, reviving long abandoned projects, and exploring new technologies. ❄ ❄ ❄ ❄ ❄ I've spent a few days at the DDD Europe conference, which was a very enjoyable event. With all the changes to programming due to LLMs, I suspect Domain-Driven Design is going to be one of those things that will continue to be useful, indeed may become even more important. The highlight of the conference was the opening keynote by Eric Evans, who gave a fascinating description of some of his experimentation with LLMs over the last couple of years. Once the video for that talk becomes available, I'll link to it - hopefully it won't be too long. I also particularly enjoyed talks from Violetta Pidvolotska, Kiran Prakash, Tom de Wolf, and Chelsea Troy. Gien Verschatse interviewed Eric Evans and me for an hour so so - again I'll pass that link on when the video gets published. One snippet that stood out to me was from Chelsea Troy. The main thrust of her talk was managing the context window of LLMs so that it was kept in a healthy state. Much of what she said was familiar, but one thing I hadn't thought about was her thoughts about the different registers of conversations with LLMs. These registers are different styles of con ## Building a Global, Event-Driven Platform: Our Ongoing Journey, Part 1 DevFeed: [Building a Global, Event-Driven Platform: Our Ongoing Journey, Part 1]() Original publisher: [Read original article]() Author: Dejan Menges Published: 2026-01-09T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [event driven](), [Domain-driven design (DDD)](), [Latency](), [Software](), [Development]() Tags: [architecture](), [ddd](), [development](), [distributed](), [domain-driven-design](), [event-driven](), [latency](), [patterns](), [scale](), [software]() ### AI overview Vinted describes why its growing platform outgrew a monolithic architecture, citing regional latency, unpredictable load, large failure domains, and tangled responsibilities. The article outlines the use of Domain-Driven Design to identify domains and guide team and architecture restructuring, followed by a move toward event-driven communication and sagas. ### Source excerpt A few years ago, our platform reached a point where the way we'd always built software simply wasn't enough anymore. The monolith that powered our early success had served us well, but as the business expanded across the continent, it started showing real limits. Global growth forced us to confront problems we couldn't ignore: latency across regions, unpredictable load patterns, and an architecture that didn't match the scale of the company. We needed to rethink how the entire system worked, from the shape of our data to the boundaries between teams. ## Deployment-Driven Development DevFeed: [Deployment-Driven Development]() Original publisher: [Read original article]() Published: 2024-11-11T22:57:13Z Content type: article Language: en Sources: [Brave New Geek]() Topics: [Deployment](), [Domain-driven design (DDD)](), [software-architecture](), [Platform Engineering](), [Testing](), [Tech Debt](), [sdlc]() Tags: [architecture](), [ddd](), [deployment](), [deployment-driven-development](), [development-process](), [devops](), [domain-driven-design](), [konfigurate](), [platform-engineering](), [qa](), [sdlc](), [security](), [tech-debt]() ### AI overview The article introduces Deployment-Driven Development as a complement to Domain-Driven Design, focusing on delayed feedback and delivery obstacles that affect software architecture, testing, security, compliance, and production readiness. ### Source excerpt Most people use "DDD" to refer to Domain-Driven Design, which is a useful tool for thinking about API boundaries and system architecture. It provides a way to map a business problem into software. At Real Kinetic, we regularly help our clients utilize Domain-Driven Design as well as other strategies to architect their systems, avoid some of the pitfalls of DDD, and build an effective foundation for designing software. But this DDD only speaks to one small aspect of building and shipping software. ## Introduction to Domain-Driven Design and Domain Models DevFeed: [Introduction to Domain-Driven Design and Domain Models]() Original publisher: [Read original article]() Author: Renlester De Guzman Published: 2024-02-27T05:18:38Z Content type: tutorial Language: en Sources: [Kogan.com]() Topics: [Domain-driven design (DDD)](), [Databases](), [Architecture & Design]() Tags: [architecture](), [database](), [ddd](), [domain-driven-design](), [leadership](), [process]() ### AI overview An introduction to Domain-Driven Design (DDD), covering its focus on business models, core domain-model concepts, and the contrast between domain-level and database-level business logic. ### Source excerpt In the complex landscape of software development, aligning design methodologies with business needs is crucial. Domain-Driven Design (DDD) emerges as a key approach in addressing this alignment, especially in projects characterized by intricate business rules and processes. This methodology stands in contrast to traditional practices, such as embedding business logic within databases, offering a more adaptable and business-focused perspective. Section 1: Understanding Domain-Driven Design Definition and Focus DDD is centered around developing software that intricately reflects the business models it aims to serve. It emphasizes a deep understanding of the business domain, ensuring that the software development process is driven by this knowledge, thereby facilitating a common language between developers and business stakeholders. History and Evolution Pioneered by Eric Evans, DDD has grown from a set of principles into a comprehensive approach, widely recognized for its ability to tackle complex business challenges through software. Aligning Design with Business Needs The essence of DDD lies in its focus on business-relevant software development, a principle that aligns closely with the need for software to be adaptable and directly linked to business objectives. Section 2: Core Concepts of Domain-Driven Design In DDD, concepts like Entities, Value Objects, Aggregates, Domain Events, Repositories, and Bounded Contexts form the foundation of a robust domain model. Entities and Value Objects: Entities are defined by their identity, playing a crucial role in maintaining business continuity, while Value Objects add depth and integrity to the domain model. Domain Model vs Database-Level Logic The decision to embed business logic in the domain model rather than in the database is pivotal. Traditional database-centric approaches can lead to scalability challenges and obscure the business logic from the development team. A domain-centric approach, as proposed by DDD, enhanc ## jOOQ DAOs, CRUD Access, and the N+1 Query Problem DevFeed: [jOOQ DAOs, CRUD Access, and the N+1 Query Problem]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-06T13:41:52Z Content type: opinion Language: en Sources: [jOOQ]() Topics: [CRUD](), [SQL](), [Domain-driven design (DDD)](), [Transactions](), [account]() Tags: [account](), [api](), [crud](), [dao](), [data](), [ddd](), [developers](), [join](), [jooq](), [jooq-in-use](), [optimisation](), [repository](), [sql](), [transactions]() ### AI overview This opinion article examines jOOQ's DAO API and the tendency to use DAOs or repositories for quick CRUD access. It argues that this approach can obscure query design and lead to inefficient patterns such as N+1 queries, while showing how explicit SQL and bulk operations can improve query structure and performance. ### Source excerpt jOOQ's DAO API is one of jOOQ's most controversial features. When it was first implemented, it was implemented merely: There's a strong hint about the third bullet given how popular Spring Data's repository "pattern" is. A lot of developers just want to quickly fetch and store data, without giving individual queries much thought. A fun ... Continue reading To DAO or not to DAO -> ## Pleasant debugging with GDB and DDD DevFeed: [Pleasant debugging with GDB and DDD]() Original publisher: [Read original article]() Published: 2022-07-17T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [debugging](), [configuration](), [Terminal](), [Linux](), [Scripting](), [Text-based user interface]() Tags: [article](), [configuration](), [ddd](), [debugger](), [debugging](), [gdb](), [linux](), [scripting](), [terminal]() ### AI overview This article presents configuration and scripting techniques for making GDB debugging more pleasant on Linux and BSD systems. It compares several interface-customization approaches and focuses on using the Data Display Debugger (DDD), including workarounds for its compatibility problems with recent GDB versions and its remote SSH support. ### Source excerpt 2022-07-17 GDB is an old and ubiquitous debugger for Linux and BSD systems that has extensive language, processor, and binary format support. Its interface is a little cryptic, but learning GDB pays off. This article is a set of miscellaneous configuration and scripting tricks that illustrate reusable principles. It assumes you're familiar with the basics of debugging, like breakpoints, stepping, inspecting variables, etc. Table of contents By default, GDB provides a terse line-based terminal. ## Implementing Equality in Ruby DevFeed: [Implementing Equality in Ruby]() Original publisher: [Read original article]() Author: Denis Defreyne Published: 2022-05-26T14:00:01Z Content type: tutorial Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Ruby](), [Programming](), [Domain-driven design (DDD)](), [Rails](), [Object-relational mapping]() Tags: [ddd](), [identity](), [model](), [models](), [orm](), [programming](), [ruby]() ### AI overview This article explains how equality works in Ruby, including the roles of #==, #eql?, #equal?, and #===. It presents general implementation patterns for entities, whose identity is based on an explicit ID, and value objects, whose identity is determined by their complete value. It also relates these patterns to domain-driven design and Ruby on Rails ActiveRecord models. ### Source excerpt Ruby is one of the few programming languages that get equality right. I often play around with other languages, but keep coming back to Ruby. This is because Ruby's implementation of equality is so nice. Let's walk through all forms of equality in Ruby and how to implement them. ## Памятка начинающего программиста DevFeed: [Памятка начинающего программиста]() Original publisher: [Read original article]() Published: 2016-11-09T09:12:28Z Content type: opinion Language: ru Sources: [Blog by Michael Dubakov]() Topics: [ASP.NET](), [Domain-driven design (DDD)](), [Artificial Intelligence]() Tags: [ai-ml](), [asp-net](), [ddd]() ### AI overview A Russian-language advice article for programmers with a few years of experience. It recommends seeking responsibility early, following industry trends, learning English, blogging, studying broader software concepts, building personal projects, and avoiding prolonged outsourcing work. ### Source excerpt Я часто получаю резюме от программистов. Возьму на себя смелость дать несколько конкретных советов тем, кто в профессии пару лет. Конечно, советы только для тех, кто хочет стать отличным программистом. 1. Первую работу найти непросто. Раньше было очень непросто, сейчас, конечно, все гораздо легче. Но если у вас получится, постарайтесь не попасть сразу в огромную корпорацию. В таких местах слишком много формализма, устаревших процессов и мест, где можно не напрягаться. И нет ничего хуже для новичка быть в расслабленной атмосфере на задворках аутсорса. Лучше выбрать стартап с маленькой зарплатой и большой неопределенностью, пока вы можете себе это позволить. Там у вас будет больше ответственности и развитие будет идти гораздо быстрее. Год за два :) 2. Всеми правдами и неправдами избегайте старых технологий. ASP.NET, O/R mappers, ExtJS, MSSQL, Oracle, Windows -- оставьте вот это все ветеранам. Вам может быть пока сложно понять, куда все двигается, но постарайтесь интересоваться трендами отрасли. Не все новое одинаково полезно, но со временем вы научитесь выбирать и лучше поймете, чего вы хотите и что вам интересно. 3. Учите английский. Вы как минимум должны научиться свободно читать техническую литературу. Без этого крайне сложно стать хорошим программистом. 4. Заведите блог. Вам кажется, что вам не о чем писать. Конечно же, это не так. Любое новое знание, усвоенное вами и выраженное письменно с учетом ваших личных переживаний и мыслей, может быть полезно другим. Напишите 100 постов. Потом можно решить, продолжать или нет. 5. Не зацикливайтесь на книгах о технологиях. Конечно, у вас есть явная потребность углубиться в ASP.NET на работе, но разбавляйте такие книги более абстрактной литературой. Почитайте про ООП и ФП, почитайте про дизайн систем, почитайте о разных концепциях (микросервисы, конкурентность, DDD, AI/ML). 6. Программируйте дома. Начните свой проект. Неважно какой. Простое мобильное приложение. Движок для сайта. Трекер расходов. Выбор следующего фильма для п ## Eric Evans in the house DevFeed: [Eric Evans in the house]() Original publisher: [Read original article]() Author: Nicolai Høge Published: 2015-03-10T14:37:49Z Content type: article Language: en Sources: [Finn.no]() Topics: [Domain-driven design (DDD)](), [Architecture & Design](), [Enterprise Architecture]() Tags: [architecture](), [course](), [ddd](), [domain-driven-design](), [enterprise-architecture](), [workshop]() ### AI overview FINN.no invited Eric Evans for a week of strategic Domain-Driven Design courses, workshops, and a presentation. The article describes the organization's effort to move from a monolith toward a more flexible and scalable architecture. ### Source excerpt In our continuing quest to break up our old monolith and create a more flexible and scalable architecture, we have realized that we need to look at some new tools and methods. One of the more promising approaches was Domain Driven Design, a term coined by Eric Evans in his Big Blue Book Quite a few people in FINN has read (at least parts of) the Domain-Driven Design book, and we did some preliminary efforts to map our domains and look at our bounded contexts. We quickly realized that this was a very complex exercise, even with highly motivated tech and product people present. We figured we needed some help to get us on the right track. If you need help and information about DDD, why not get it straight from the horse's mouth? So we got Eric Evans to visit us for a week at the end of February. We needed to make the most of our time with Eric, so we set up a rather extensive agenda: Day Subject Attending Monday Strategic Domain Driven Design Course FINNs CTO, our functional product directors, the members of our enterprise architecture group including our Chief Enterprise Architect, several key developers and a couple of our international friends from Schibsted Classified Media Tuesday Strategic Domain Driven Design Course cont'd Same as Monday Wednesday Workshop: Ad concept and our miscellaneous vertical Chief Enterprise architect, EA group, Functional Product Director, Product Owner, Lead Developers Thursday Workshop: Job vertical and company profile Chief Enterprise architect, EA group, Functional Product Director, Product Owner, Lead Developers Friday Presentation for everyone in FINN.no, plus workshop: Communications Chief Enterprise architect, EA group, Functional Product Director, Product Owner, Lead Developers The course on Monday and Tuesday was extremely helpful in getting everyone up to speed on the terms and method of strategic domain driven design. The workshops the rest of the week focused on understanding the challenges involved in each area, and trying ## Modelling Is Everything DevFeed: [Modelling Is Everything]() Original publisher: [Read original article]() Author: Martin Thompson (noreply@blogger.com) Published: 2011-09-02T18:23:00Z Content type: opinion Language: en Sources: [Mechanical Sympathy]() Topics: [Domain-driven design (DDD)](), [systems](), [Development](), [Code](), [Cache](), [cpu](), [Network]() Tags: [code](), [ddd](), [design](), [development](), [domain-driven-design](), [modelling](), [performance](), [systems]() ### AI overview The article argues that modelling what needs to be implemented is the most important step in software development, especially when building high-performance systems. It connects Domain-Driven Design with modelling the problem domain and explains that understanding CPU, memory, storage, cache, and network behavior can improve correctness and performance. ### Source excerpt I'm often asked, "What is the best way to learn about building high-performance systems"? There are many perfectly valid answers to this question but there is one thing that stands out for me above everything else, and that is modelling. Modelling what you need to implement is the most important and effective step in the process. I'd go further and say this principle applies to any development and the rest is just typing :-) Domain Driven Design (DDD) advocates modelling the domain and expressing this model in code as fundamental to the successful delivery and ongoing maintenance of software. I wholeheartedly agree with this. How often do we see code that is an approximation of the problem domain? Code that exhibits behaviour which approximates to what is required via inappropriate abstractions and mappings which just about cope. Those mappings between what is in the code and the real domain are only contained in the developers' heads and this is just not good enough. When requiring high-performance, code for parts of the system often have to model what is happening with the CPU, memory, storage sub-systems, or network sub-systems. When we have imperfect abstractions on top of these domains, performance can be very adversely affected. The goal of my "Mechanical Sympathy" blog is to peek at what is under the hood so we can improve our abstractions. What is a Model? A model does not need to be the result of a 3-year exercise producing UML. It can be, and often is best as, people communicating via various means including speech, drawings, illustrations, metaphors, analogies, etc, to build a mental model for shared understanding. If an accurate and distilled understanding can be reached then this model can be turned into code with great results. Infrastructure Domain Models If developers writing a concurrent framework do not have a good model of how a typical cache sub-system works, i.e. it uses message passing to exchange cache lines, then the framework is unlikely to ## Code Refurbishment DevFeed: [Code Refurbishment]() Original publisher: [Read original article]() Author: Martin Thompson (noreply@blogger.com) Published: 2011-08-20T16:02:00Z Content type: opinion Language: en Sources: [Mechanical Sympathy]() Topics: [Refactoring](), [Code](), [Code quality](), [Test-driven development]() Tags: [code](), [code-quality](), [ddd](), [refactoring](), [refurbishment](), [tests](), [unit-tests]() ### AI overview The article distinguishes refactoring from broader structural redevelopment. It defines refactoring as behavior-preserving changes that improve code structure, quality, and maintainability, while noting that larger changes may reuse existing code without being a complete rewrite. ### Source excerpt Within our industry we use a huge range of terminology. Unfortunately we don't all agree on what individual terms actually mean. I so often hear people misuse the term "Refactoring" which has come to make the business in many organisations recoil in fear. The reason for this fear I've observed is because of what people often mean when misusing this term. I feel we are holding back our industry by not being disciplined in our use of terminology. If one chemist said to another chemist "we are about to perform titration", both would have a good idea what is involved. I believe computing is still a very immature science. As our subject matures hopefully we will become more precise and disciplined in our use of terminology and thus make our communication more accurate and effective. Refactoring is a very useful technique for improving code quality and clarity. To be precise it is a behaviour preserving change that improves a code base for future maintenance and understanding. A good example would be extracting a method to remove code duplication and applying this method at every site of the duplication, thus removing the duplication. Refactoring was first discussed in the early 1990s and became mainstream after Martin Fowler's excellent "Refactoring" book in 1999. Refactoring involves making a number of small internal changes to the code structure. These changes will typically not have any external impact. Well written unit tests that just assert externally observable behaviour will not change when code is refactored. If the external behaviour of code is changing when the structure is being changed then this is not refactoring. Now, why do our business folk recoil in fear when this simple and useful technique of "refactoring" is mentioned? I believe this is because developers are actually talking about a much more extensive structural redevelopment technique that does not have a common term. These structural changes are often not a complete ground-up rewrite because much