The Curse of Service Object
summary
Argues that widely used service objects are a harmful, ill-fitting abstraction that grow inward into monsters (one GitLab service swells to 200 lines), and demonstrates a concrete alternative: use the visual method O in pictures to classify work, move business rules into models, push complex mutations into mutators, and isolate external calls into small manager classes. Shows code examples from real repos, explains controllers keep application concerns, and makes services plain stateless procedures named for activities.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 3:00O in Pictures method explained
- 10:07What developers say about service objects
- 12:37Roots of service objects concept
- 18:21Analyzing service objects in practice
- 27:53The curse of service objects
- 32:18Refactoring with modular approach
- 39:25Q&A session begins
related talks
30mYour Service Layer Needn't be Fancy, It Just Needs to Exist
40mWorkshop - Simplifying Code: Monster to Elegant in Less Than 5 steps
33mServices and Rails: The Shit They Don't Tell You
28mServices and Rails: The Shit They Don't Tell You
23mAbstracting a Service - A Case Study in Forward Thinking with SOA
34mSimple and Elegant Rails Code with Functional Style
36mDo Proper Monoliths before You Do Microservices!
34mSOA and the Monolithic Rails App Anti-Pattern