Rails – The Missing Parts • Hacker News Board

Rails – The Missing Parts

#1

Post by tomblomfield » Mon, Mar 03, 2014, 6:02 PM UTC

Rails – The Missing Parts
eng.joingrouper.com

Re: Rails – The Missing Parts

#2

Post by ollysb » Mon, Mar 03, 2014, 6:22 PM UTC

Perhaps because it's written with examples in java but I often feel like no one in the rails community has ever read Eric Evan's Domain Driven Design[1]. It's far and away the best material I've ever seen on how to organise large code bases. It covers pretty much every suggestion that I've seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things that have been done before.

[1] http://www.amazon.com/Domain-Driven-Design-Tackling-Complexi...

Re: Rails – The Missing Parts

#3

Post by hiphopyo » Mon, Mar 03, 2014, 6:30 PM UTC

ollysb wrote: post #2

Perhaps because it's written with examples in java but I often feel like no one in the rails community has ever read Eric Evan's Domain Driven Design[1]. It's far and away the best material I've ever seen on how to organise large code bases. It covers pretty much every suggestion that I've seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things…

Is http://tech.taskrabbit.com/blog/2014/02/11/rails-4-engines/ another one of those?

Re: Rails – The Missing Parts

#4

Post by antonydenyer » Mon, Mar 03, 2014, 6:30 PM UTC

ollysb wrote: post #2

Perhaps because it's written with examples in java but I often feel like no one in the rails community has ever read Eric Evan's Domain Driven Design[1]. It's far and away the best material I've ever seen on how to organise large code bases. It covers pretty much every suggestion that I've seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things…

probably because in most cases the domain model doesn't get that complex.

Re: Rails – The Missing Parts

#5

Post by antonydenyer » Mon, Mar 03, 2014, 6:31 PM UTC

ollysb wrote: post #2

Perhaps because it's written with examples in java but I often feel like no one in the rails community has ever read Eric Evan's Domain Driven Design[1]. It's far and away the best material I've ever seen on how to organise large code bases. It covers pretty much every suggestion that I've seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things…

probably because in most cases the domain model doesn't get that complex.

Re: Rails – The Missing Parts

#6

Post by tomblomfield » Mon, Mar 03, 2014, 6:34 PM UTC

ollysb wrote: post #2

Perhaps because it's written with examples in java but I often feel like no one in the rails community has ever read Eric Evan's Domain Driven Design[1]. It's far and away the best material I've ever seen on how to organise large code bases. It covers pretty much every suggestion that I've seen from the rails community. Sometimes the rails community can feel like the fitness industry, everybody just rebranding things…

Sure - I don't think anyone in the Rails world is claiming to have invented these principles.

The problem is that Rails ships with a very limited set of core architectural concepts, and many inexperienced Rails developers feel like they've got to cram all of their code into a Model, View or Controller.

Once your codebase reaches a certain complexity, principles from other programming paradigms are extremely useful.

Re: Rails – The Missing Parts

#7

Post by tzaman » Mon, Mar 03, 2014, 6:46 PM UTC

We tried using DHH's concerns in place for interactors, but ditched them for PORO/service objects because they can be tested outside Rails.

Re: Rails – The Missing Parts

#8

Post by casey_lang » Mon, Mar 03, 2014, 6:47 PM UTC

Along the same line but heavier weight than 'Interactor' is 'ActiveInteraction'[1].

Responds in much the same way active record does, allowing validations, errors, forms built from interaction objects, etc.

[1] http://github.com/orgsync/active_interaction

Re: Rails – The Missing Parts

#9

Post by pothibo » Mon, Mar 03, 2014, 6:48 PM UTC

One thing I really enjoy with this post is the conclusion. It doesn't try to tell you it's the only way, just that it's the way they found to fix their problem with the constraints they had, as it should be.

Rails is easy to extend, people often forget that. Great post.

Re: Rails – The Missing Parts

#10

Post by Axsuul » Mon, Mar 03, 2014, 6:49 PM UTC

I've been looking into incorporating this pattern into my larger Rails apps as well. Another benefits of interactions is DRYing up your code for use in APIs. Some of the more popular interactor gems:

https://github.com/orgsync/active_interaction https://github.com/cypriss/mutations