3 ms·
services are IMO the biggest misfire of an attempted rails convention. "service" is completely domain agnostic and because there's no standard API like there is
by LesZedCB 3y ago
services are IMO the biggest misfire of an attempted rails convention. "service" is completely domain agnostic and because there's no standard API like there is for controllers or model, the "service" API ranges from `MyService.call` to `MyService.new.call` `MyService.do_thing` etc etc.
service became the junk drawer of junk drawers even worse than lib because people at least 'believe' there is supposed to be a convention when there isn't. at least you know lib is kinda wild west.
rails has failed to channel applications into domain logic once it scales past start-up rapid development to a huge team of ICs
- nightpool 3y agoI agree with the former, but I absolutely can't agree with the latter. Services aren't necessary to scale up Rails applications. Plenty of people get along just fine with plain old model-view-controller architectures.
- deleted 3y ago[deleted]