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

[–] d23dro@lemmy.sdf.org 1 points 6 months ago* (last edited 6 months ago)

I would call them “agents” at a class layer and encapsulate the logic specific to each domain in its own class. Completely arbitrary but in my mind: adapters - call other web services

dao - database calls

agent - responsible for stitching the pieces all together and doing the actual business logic.

Example: OpenWeatherAdapter - call the OpenWeather API. No business logic. H2SelectDao - get user preferences from an internal database. No business logic.

WeatherAgent(openWeatherAdapter, h2SelectDao) - All the business logic.

Note: this is in context of a API service like a middleware.