this post was submitted on 30 May 2024
16 points (100.0% liked)

Experienced Devs

3983 readers
1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 2 years ago
MODERATORS
 

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 are viewing a single comment's thread
view the rest of the comments
[–] tatterdemalion 4 points 5 months ago (1 children)

Stealing from "Domain Driven Design", I think calling them "domain objects" is appropriate.

[–] vvv 1 points 5 months ago (1 children)

that's a good call actually. I got pretty hung up on domain objects being mostly data classes, but one approach is to have them perform business logic themselves.

[–] tatterdemalion 1 points 5 months ago

Perhaps "domain modules" if you want to be more agnostic about the actual shape of the code.