Experienced Devs

4008 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:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 2 years ago

MODERATORS

snowe@programming.dev

jmk1ng@programming.dev

drewsiferr@programming.dev

What do you call application modules that are responsible for business logic? (programming.dev)

submitted 6 months ago by vvv@programming.dev to c/experienced_devs@programming.dev

18 comments fedilink hide all child comments

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

[–] BehindTheBarrier@programming.dev 6 points 6 months ago* (last edited 6 months ago) (1 children)

It's not that universal, but we have named a few things "Engines", for example Balancing Engine. We also use services, but they are actually independent programs that performs jobs. Engine are used in other places, such as the ViewModels, or in the services.

We put them in the DomainModel project which most things reference though. That's were most basic functionality and shared resources end up if they are used across Client/Service/Backend projects. So Domain / DomainModel might be a thing to use as well, if you want a specific namespace for that kind of use.

[–] vvv@programming.dev 1 points 6 months ago

Thanks for that, I think Engines is winning in my mind so far!