InfoQ Homepage Domain-Driven Design Content on InfoQ
Interviews
RSS Feed-
Eric Evans and Brian Foote discuss the state of Software Design
Eric Evans (Creator of Domain-Driven Design), and Brian Foote (Big Ball of Mud, Patterns Languages of Program Design), discuss the current state of software design, reminisce about the Small talk good old days, explain patterns from Domain-Driven Design, UML, Big Balls of Mud, and more.
-
Eric Evans on How Technology Influences DDD
Eric Evans shares his view on how the last trends in technology, such as NoSQL, functional languages, thick browser-based client, JSON and others, make him rethink some of the DDD concepts.
-
Jez Humble on Continuous Delivery
In this interview at Agile 2011, Jez Humble discusses continuous delivery and the deployment pipeline, emphasizing the importance of feedback and automating tests at every level to validate deployments. Gone are the days of massive acceptance test scripts. He also talks about the evils of feature branching, and speaks on the DevOps practices to collaborate all the way through the delivery cycle.
-
Udi Dahan on CQRS, DDD and NServiceBus
Udi Dahan talks about Command Query Responsibility Segregation (CQRS) and its relationship to Domain Driven Design (DDD). Dahan also discusses his project, the NServiceBus. NServiceBus is an open-source service bus for Microsoft's .NET environment. In many ways, NServiceBus works like Microsoft's Windows Communication Foundation (WCF) and can be used instead of WCF in some cases.
-
Eric Evans on the State of DDD
At QCon San Francisco, 2008, Eric Evans answers questions about his recent activities and the evolution of DDD. During the interview he responds to questions about the relationship of DDD to usability, to FIT and FITnesse type testing, technology tools, and domain-specific languages. He also speaks about the DDD community as a whole.
-
Eric Evans Interviews Greg Young on the Architecture of a Large Transaction System
Eric Evans, the author of Domain Driven Design, interviews Greg Young about the architecture implemented for a system processing tens of thousands of transactions per second. It's not just the sheer number of transactions that is challenging, but the time constraints imposed are those specific to real-time systems. Greg reveals some of the architecture elements of the system's design.
