[gashaw]

Ruby is great, Rails is good enough.

The main issue with Rails (it's the same with other frameworks) is that it discourages from doing proper design. The only design decision you make is where to put a piece of code, which is ridiculous ("Fat models, skinny controllers" is a bad design heuristic.)

Following Rails conventions works for small (simple) applications, but over time you arrive at a point where no one understands the whole thing. At this point someone suggests moving to microservices, and all hell breaks loose.

[richjdsmith]

Adding a services directory with logic moved out from my models into POROs helped a lot for taming the mess.

[yebyen]

Can you share a link about what you mean by this?

I went searching but came up pretty empty ... do you literally mean adding an "app/services" directory, is that all? Where you put classes related to external dependencies that aren't ActiveRecord?

[nitrogen]

I don't agree with the pattern discussed here and actually like smart models (I want to tell my model "do the thing", not write and babysit a bureaucratic coordinator service. But, since you asked, it's common in other frameworks like Spring to have a "service" layer that sits between your controller and model layers. The service layer has the logic, and the models are just storage.

[yebyen]

That's common in Rails too. Except I don't think it's necessary to make it a go-between.

Where controllers have simple interactions with models (which represent database structures, and may have logic in them) you let the controller have direct access to the model.

Models can grow to be too complex, this is where having a concept of named "Concerns" can come in handy, even if you won't use them in another model, it can lift some complexity out of your model and put it into a logical group.

Services, in my view, are akin to models. Some of them may use models behind the scenes. More of them actually represent an external service, which might be an external database that lives behind a web service, an API. Or it might be an LDAP service. (Or it might be a command pattern)

I agree with smart models, if the complexity does belong to the model, then why not let it live there. It sounds like the service layer you're describing is a needless ceremony for "managing complexity" – I'll bet it was a concept that was introduced to your group by an architect.

[gashaw]

Don't you mind having 5000+ LOC model? Methods being redefined because the class is huge and the developer didn't notice the existing method?

[notafrog]

Yep. That has been my experience with Django as well.

[sidcool]

I have the exact opposite view that I have mentioned in another comment on this post. "Rails is amazing, Ruby is good'.