Hey thanks for writing this. It reminds me about form objects and service objects (for when you are saving and retrieving respectively). It is pretty similar, but I like the name of "cases".
It is interesting to see how many devs are changing on Rails from the common pattern to use objects (following SOLID), Rails projects got success, the time goes by and the projects became hard to maintain so it was needed to go back to foundations. It is good, don't know if Rails 6 will introduce some guidance about these topics (I don't think so).
Really glad that you liked it =)
Because there is no guidance/common way of writing business logic on rails, what I've seen so far is that each company does it in a different way.
Using use cases like I described in this blog post is one of them.
btw, I also recommend to check some design patterns in ruby: github.com/davidgf/design-patterns...
it's quite interesting =)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.