RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  
 

Domain Driven Design for Rails Developers. Part 3: Aggregates.

Posted by vsavkin on May 09, 2012 — 1 comment
You start with nicely designed groups of objects. All the objects have clear responsibilities, and all interactions among them are explicit. Then, you have to consider additional requirements, such as transactions, integration with external systems, event generation. Soon you end up with a bunch of interconnected objects without clear boundaries. Maintaining this mess becomes harder and harder. Thankfully, Domain Driven Design provides a good remedy for this situation: Aggregates. Read more

Comments

“” Like i said on twitter... if you wrote a book, i'd buy it! Your articles on RubySource are excellent!mariozig - May 15, 2012 17:45
“”

Post a Comment

Comment abilities for non registered users are currently deactivated, pending time to add a proper CAPTCHA to solve the escalating spam problem. Sorry!