RubyFlow The Ruby and Rails community linklog

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

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!

Post a comment

You can use basic HTML markup (e.g. <a>) or Markdown.

As you are not logged in, you will be
directed via GitHub to signup or sign in