Tracking change and innovation in the enterprise software development community
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Floyd Marinescu on Dec 11, 2006
The most complicated aspect of large software projects is not the implementation, it is the real world domain that the software serves. Domain Driven Design is a vision and approach for dealing with highly complex domains that is based on making the domain itself the main focus of the project, and maintaining a software model that reflects a deep understanding of the domain. The vision was brought to the world by Eric Evans in his book "Domain Driven Design". Eric's work was based on 20 years of widely accepted best practices in the object community, as well as Eric's own insights.
Despite the importance of Domain Driven Design, not many people are aware of it, which is why InfoQ commissioned the writing of a 100 page mini-book: Domain Driven Design Quickly, and like all InfoQ books is available for free download as well as print-purchase. The book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' 576 page book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums. Main topics in the book include:Learning to be a Good Product Owner: Foundation Skills
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
Visit SOA Appliance Comparison Site
*Video Usage Model Tutorials
*Comparison to IBM DataPower X150
*Performance Benchmarks/Webinars
*Replace DataPower Program
FREE 1:1 Swap & Migration Services
I doubt.. :)
Although Eric's book came out in 2003, it seems that 2007 will the year Domain Driven Design becomes widely known.
I agree: 2007 is likely to be a big year for DDD. Having just coming back from The Spring Experience conference, we had a lot of interest in the DDD track. Basically the ideas of DDD are timeless, and there is certainly growing understanding and interest.
Floyd, thanks for getting this material out there.
I agree. Actually it IS printable :)
Actually it's not, that was a temporary mistake. While we want to make the information freely available for reading, one should buy the print book for ultimate convenience. Buying the book will then fund further mini-book and content efforts on InfoQ.
Eric Evans also gave two talks on DDD at Javapolis in Antwerp, Belgium, and I was pleasantly surprised by the public attention.
Who is the author of the mini book ?
BR,
~A
I'll second that question; who is the author?
My impressions on what I've read so far: the first two chapters are surprisingly long-winded for a "Quickly" book and seem to preach to the choir, and there are a fair number of typos or missing words. Cut to chapter 3 if you want to get started "quickly".
Domain-Driven Design Quickly was produced by InfoQ.com, summarized primarily by Abel Avram and with Floyd Marinescu as managing editor. Special thanks to Eric Evans for his support and Vladimir Gitlevich and Dan Bergh Johnsson for their detailed reviews.
Hello, I would like to know if I could translate to portuguese the key parts from your book and publish it in a brazilian forum?
Buying the book will then fund further mini-book and content efforts on InfoQ.
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.
10 comments
Watch Thread Reply