blog-post-anatomy-of-a-service-object-in-rails

http://technology.stitchfix.com/blog/2015/06/02/anatomy-of-service-objects-in-rails/

blog-post-anatomy-of-a-service-object-in-rails#high-level-overview1

• Do not store state
• use-instance-methods-not-class-methods
• There should be very-few-public-methods
• Method parameters should be value objects, either to be operated on or needed as input
• Methods should return a rich-result-object and not a boolean
• Dependent service objects should be accessible via private methods, and created either in the constructor or lazily

blog-post-anatomy-of-a-service-object-in-rails#high-level-overview1

blog-post-anatomy-of-a-service-object-in-rails#use-instance-methods1By designing our service objects to use instance methods, it means the users of our service will depend on objects, not global symbols. Although we have to type four additional characters—.new—our code using our service can more easily adapt to change, since we can modify the class of the object we're using without changing the code that uses it. blog-post-anatomy-of-a-service-object-in-rails#use-instance-methods1

Referring Pages

People