Hi, Ah, a very interesting message and discussion in my opinion! Thanks! Since I was at that workshop, I'd like to comment. ;-) - Just because it took *me* several years to learn "enough" DDD doesn't mean that it will take you as long time to learn "enough" today. I would guess it will go much faster now. (And I actually find it hard to carefully say how long it took. What should I consider? When I first tried to understand OO? When I tried out different OO-ish designs? Only the time after the DDD book was published? And so on...) That said, coming from a data-driven approach most people will have to expect a learning curve. I also think it's very much about continous learning. We do learn all the time. And we should... - A very efficient way of learning is of course to work with someone that has the skill you would like to learn. Combinations are extremely powerful in my opinion when it comes to learning so just going for books is "too little" I think. I strongly believe that if you find the right person, he/she can probably teach you lots in days/weeks that took that person months/years to learn. - Porting your old system would probably take a lot of time, but as others here have commented it's hard to know if it's a good idea at all in this case. Perhaps/perhaps not, we can only guess. :-) But what I also think I answered that question with was that I dislike automatic approaches most often. It's probably not a good idea to just take the db-schema and generate all the classes to get a DDD-solution. Sure, it would go fast, but I would guess you haven't won that much. Most often you would prefer to rethink the whole thing, probably from a customer perspective. Or perhaps you only need to port a small portion of it... Or... Again, all we can do is guessing. :-) Good luck with your project! Cheers, Jimmy http://JimmyNilsson.com/blog/ ###