InfoQ Homepage Domain Modeling Content on InfoQ
-
Thoughtworks’ VP of Data and AI Shares Insights for Building a Robust Data Product at QCon London
During his QCon London presentation, Danilo Sato, vice president of data & AI at Thoughtworks, reemphasized the importance of using domain-driven design and Team Topologies principles when implementing data products. This ensures effective data encapsulation in a more complex landscape where data responsibilities are “shifting left” towards the developer.
-
Balancing Coupling in Distributed Systems: Vladik Khononov at DDD Europe
We have been told that coupling is bad, so we decouple everything and break everything apart into tiny services that can be changed independently. But by following this reasoning we often end up with a distributed mess, Vladik Khononov noted in his presentation at the recent DDD Europe 2020 conference in Amsterdam. Instead of fighting coupling, he proposes that we use it as a design tool.
-
Dissecting Bounded Contexts: Nick Tune at DDD Europe
There are many reasons for breaking up systems and making them more modular, Nick Tune noted in his keynote at the recent DDD Europe 2020 conference. We lower the cognitive load, teams can work independently, and from a business perspective we can do more granular investments. In his presentation, Tune discussed how by dissecting bounded contexts we can find more options when designing them.
-
The Swift Method: A Framework for Software Modernization Using DDD
The Swift Method is a set of techniques for analyzing complex legacy systems, and determining the work required to gradually modernize key components or the whole system.
-
Eric Evans Wants to Improve the Language of DDD
Eric Evans wants architects to actively engage in improving the language used when modeling and designing complex systems. Some of the fundamental terms used in DDD, such as Bounded Contexts, are often misunderstood. Evans wants to see an active community try to address these concerns, with the goal that DDD "should be a real, living body of thought."
-
Practical Domain-Driven Design with Events and Microservices - Indu Alagarsamy at QCon New York
Domain-driven design (DDD) concepts like Bounded Contexts and Messaging technologies can be used to build reliable systems that can scale with the business changes. Indu Alagarsamy recently spoke at QCon New York 2019 Conference about using the combination of well-defined bounded contexts and events to develop autonomous microservices that are flexible to adapt to the business changes.
-
Michael Feathers Wants Error Elimination to Be a Design Driver
Michael Feathers finds errors fascinating, but acknowledges that most developers don't spend a lot of time focusing on them. He also thinks most error handling is kind of giving up. Although best known for his books about working with legacy code, Feathers used his keynote presentation at Explore DDD 2018 to discuss how eliminating errors can be a design driver for software systems.
-
Finding Bounded Contexts Using Domain Storytelling
When working with Domain-Driven Design (DDD), bounded context is a core concept. Domain storytelling is a way of finding how people and systems work together within a domain which then can be used to identify the bounded contexts and how they are interconnected, Stefan Hofer and Henning Schwentner explained at the recent DDD Europe 2018 conference in Amsterdam.
-
Vaughn Vernon Uses Reactive DDD to Model Uncertainty in Microservices
Microservices and reactive systems bring with them uncertainty about messages arriving out of order, multiple times, or not at all. How to react to such uncertainty is a business decision, says Vaughn Vernon, and is best captured by modeling the uncertainty using concepts of Domain-Driven Design.
-
Eric Evans: Domain-Driven Design Even More Relevant Now
Eric Evans, author of Domain-Driven Design, said the concepts in the book he wrote in 2003 are even more relevant now than they were 14 years ago. As the range of tools and technologies has expanded, some lend themselves to the principles of DDD better than others we've had in the past. Evans said, "DDD is not about technology, but is not indifferent about technology."
-
Capture - Embed - Protect, Guidelines for Domain-Driven Design
When using the core philosophy and the practices of DDD as guidelines for software design and development, they can be summarized in three principles: Capture – Embed – Protect, Steven A. Lowe claimed in his presentation at this year’s DDD eXchange conference. Capture the domain model. Embed the model in the code. Protect the domain model from corruption from other domains.
-
Bringing the Domain Back to Software Development
If you read the business press of today, you will find that the business side of the world sees IT as an impediment that holds them back. To overcome this, we need to shift focus from the machines to the domains and start reading and learning about the domains we are working in, David West noted in his presentation at the recent DDD Europe Conference in Amsterdam.
-
Eric Evans: Is Domain-Driven Design Beneficial for Software Development?
The last couple of years the interest in Domain-Driven Design (DDD) has increased, Eric Evans noted in his keynote at the recent DDD eXchange conference in London. He thinks that we are in a time when developers care more about design, partially because we are working more with distributed systems where models have a higher value.
-
Working with Domain Experts in a DDD World
Conversations with domain experts and the language used are central in Domain-Driven Design (DDD), but often this is hard because we don’t speak the same language, explained Cyrille Martraire in his presentation at the Domain-Driven Design Europe conference earlier this year when sharing his experiences working with domain experts in DDD-driven environments.
-
Aggregates, Entities and Value Objects in Domain-Driven Design
Move as much as possible of the behaviour away from the Entities into Value Objects when working with Aggregates, As more behaviour is needed this is added as new value objects, Paul Rayner recommends in a series of blog posts covering aggregates, entities and value objects, all concepts from Domain-Driven Design (DDD).