Somewhere between API resources, queue workers, repositories, clients and serializers there is a class of … classes/modules that does the needful. Gun-to-my-head, I would call them “services” but I’m looking for a less overloaded term. Maybe capabilities? Controllers? Pick a term from the business domain? What do you call them?
You must log in or register to comment.
Stealing from “Domain Driven Design”, I think calling them “domain objects” is appropriate.
We call that business logic layer “services” at work too, for lack of a better word, but I’ll be watching over this thread for better ideas…
