Has DDD reached it's embracing tipping point or not?
Willem van Gool <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <CAKqMafw8aKSm6X-mtLSUX42d+-HZQ1CvSwXMRM8zJP_6ExW0oQ@mail.gmail.com> |
About five or six years ago, I picked up the Blue Book because I was looking for better ways to design and code the systems I was working on then. I guess that as many of you who visit this forum regularly have been on a quest to find better methods to design and code our software-systems than the transaction-scripty, data set oriented systems we have been working on for years. Unfortunately, few people within our company (size about 300) are familiar with DDD-concepts, and because of all corporate standards are based on the old, data-oriented methods of engineering and architecture, it has been really tough convincing people to 'give it a try'. On the other hand, especially with the release of Vaughn's book just recently, which is in excellent read by the way, I have the feeling that DDD is really starting to take off everywhere. This got me wondering about the world-wide adoption of DDD: has your company embraced it completely (or do you apply it often as a independent consultant), or is it still considered 'just a hype' by your peers?