Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Srini Penchikala on Jan 30, 2009
In this interview recorded at QCon San Francisco 2008 conference, Greg Young talked about how his team has been using Domain-Driven Design (DDD) concepts in their projects. He discussed how to manage domain state transitions in a Domain-Driven Design project using two different design models, one for reading data from datastore and the other for write-only command operations. He also talked about Command Query Separation (CQS) design concept to keep design cleaner and easier to test and maintain and the best practices that developers can use when working on DDD projects.
Watch: Greg Young Discusses State Transitions in Domain-Driven Design and DDD Best Practices (36 min.)
In the interview, Greg covered the following topics:
Agile Development: A Manager's Roadmap for Success
Regaining control of the data centre
Learning to be a Good Product Owner: Foundation Skills
Right Collaboration Architecture Drives Business Transformation
Great interview! A lot of what Greg said really resonates with a lot of things I've been trying to do, and his statements certainly cleared up some thoughts I was having on a) immutability, b) AOP, and c) the use of DTOs.
Thanks!
This is a superb video; I have to admit viewing this interview I had very limited knowledge about DDD, but Greg succinctly and clearly outlined his understanding and expertise. The concepts outlined are of immense value - great job.
Great interview !!
What a wonderful interview. It is so rare to come across people who can clearly state what is obviously (in retrospect) true and useful. I kinda hate all things financial, but judging by this interview I'd happily go to work for them. We surely need more of this kind of intelligence.
When using CQS in domain driven design how would you query changes made to the domain object when the domain object changes are not persisted to the database and are only in memory? i.e. I want to make a change to a customer address, I issue a command to the customer domain object, I save the customer domain object to session. I then want to update the screen with the changes. Only later when the user is happy with the total of the changes do they commit the data to the database.
A couple of possible solutions I can think of is to have a session repository, or a way of getting a query object from the domain object.
Or does CQS not apply to this type of scenario?
JdonFramework is a DDD framework , it supports model in memory, and CQRS domain events + Asynchronous, more details jdon.dev.java.net/
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
7 comments
Watch Thread Reply