InfoQ Homepage Domain Driven Design Content on InfoQ
-
Designing Reactive Systems Using DDD, Event Storming and Actors
Domain-driven design (DDD) is often used for finding boundaries (bounded contexts) around microservices. But everything in domain-driven design (DDD) is not good for microservice, Lutz Huehnken claimed in a presentation at microxchg 2018 in Berlin where he discussed how DDD, Event Storming and the Akka-based Lagom framework can be used to build reactive systems.
-
QCon London: Asynchronous Event Architectures with or without Actors
Synchronous request-response communication in microservices systems can be really complicated. Fortunately, asynchronous event-based architectures can be used to avoid this, Yaroslav Tkachenko claimed in a presentation at QCon London 2018, where he described his experiences with event-driven architectures and how Actors can be used in systems built on this architecture.
-
Notes From the DDD Europe 2018 Conference
The recently held DDD Europe 2018 conference in Amsterdam was the third in order and saw almost 700 attendees. The conference has a focus on Domain-Driven Design (DDD), and included four keynotes, 19 presentations, one track for open space and 17 sessions focused on live coding or hands-on. Notable speakers included Eric Evans, Dave Snowden, Rebecca Wirfs-Brock and Cyrille Martraire.
-
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.
-
Evolving CQRS and Event Sourced Systems
After talking with people about upgrading of CQRS and event sourced systems, Michiel Overeem came to the conclusion that many working with event sourced systems lack an understanding and don’t know how to approach the problem. At the recent DDD Europe 2018 conference in Amsterdam he described how this was a trigger for him to do an exploratory research on how to evolve this kind of system.
-
Eric Evans: Practicing Domain-Driven Design
For Eric Evans, who gave a keynote at the recent DDD Europe 2018 conference in Amsterdam, it’s important to explore and practice building software. He enjoys working with strategic patterns in Domain-Driven Design (DDD), but what he finds really interesting is taking a difficult domain and reason about it differently; breaking out of the mental box trying to find new concepts.
-
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."
-
Selecting an Event Architecture
When designing a distributed system, maybe based on microservices, and you are considering an event architecture, there are several models and technologies available. When choosing how to implement the architecture the non-functional requirements are a main factor, David Dawson claims when describing different styles of event architectures in a recent blog post.
-
Process Managers in Event-Based Systems
Publishing events to notify about changes in a domain keeps different domains decoupled from each other, but if there really is a logical flow of events it becomes implicit and hard to follow. A better solution is to use a Process Manager to keep track of the overall process, Bernd Rücker stated in his presentation at this year’s DDD eXchange conference.
-
Susanne Kaiser on Microservices Journey from a Startup Perspective
Susanne Kaiser, CTO at Just Software, spoke at the recent QCon New York 2017 Conference about the transformation process her team went through to transition from a monolithic application architecture to microservices model.
-
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.
-
From Microliths to Microsystems: Jonas Bonér at QCon London
At QCon London, Jonas Bonér, CTO at Lightbend, presented “From Microliths to Microsystems”, and explored microservices from first principles, and discussing the architectural style in the context of distributed systems. Key takeaways included: avoid building ‘microliths’, and instead create systems that are resilient and elastic; and practice events-first Domain-Driven Design (DDD).
-
The Importance of Patterns in DDD
There are lots of patterns outside of Domain-Driven Design (DDD) that are important to know, and they will help you design better systems, Cyrille Martraire claimed in his presentation at the recent DDD Europe Conference in Amsterdam when discussing the importance of patterns.
-
microXchg Microservices Conference Day One Summary: DDD, Platforms, and Organisational Impact
At the microXchg conference in Berlin, a group of software development practitioners shared their latest learnings about the microservice architectural style. Topics discussed included functional service design, integrating DDD and REST, creating microservice-powered websites using transclusion, choosing a microservice platform, and the organisational and people impact of microservices.