Service Objects (No More Fat Models)

Re:Service Objects (No More Fat Models) by rorykoehler on Sunday November 13, 2016 @09:27AM (#12943429)

This is how I get all my teams to work. The code goes in app/services folder though. Lib is for 3rd party stuff.

A project I worked on last year also implemented what they called 'use-cases' which were essentially model-view classes to extract and prepare data for the views.

[ Parent | on HN ]

Re:Service Objects (No More Fat Models) by gjorquera on Sunday November 13, 2016 @12:49PM (#12944541)

Yeah, app/services might be a better fit.

I'm glad that there are teams stearing away from fat models.

Or fat anything, actually, as they usually violate the SRP.

How did the 'use cases' work for you?

[ Parent | on HN ]

Re:Service Objects (No More Fat Models) by rorykoehler on Tuesday November 15, 2016 @03:54AM (#12956600)

Use cases are essentially classes that hold large sql queries etc to prepare data for use in the view. We were working on analytics visualisations for large volumes of data.

[ Parent | on HN ]