Reputation: 987
Where should i put a logic that is going to be used in many command/query handler?
So I have a method that receives an array of ids of a given entity in our database, I search in the db for those ids, and the ones that were not found I store them in DB, after that I return an array of those entities containing the ones that were already created and the new ones.
Since this entity has relations with a diversity of other entities, this logic is expected to be consumed by many command/query handlers, where should I put this logic?
- Create a service file that will be imported and called from each domain query/command handler?
- Create a command-handler doing this logic and call this command-handler from the other hanlders ( i think this is an anti-pattern right? )?
Upvotes: 0
Views: 684
Answers (1)
Reputation: 663
I would definitely create a class which encapsulates your logic and inject this class in the command/query handlers.
At first glance, maybe creating a repository class for this entity would be great too, you could encapsulate this logic there.
Upvotes: 1
Related Questions
- Preferred way of handling "Event Sourcing" in NestJS CQRS recipe
- Where better to keep common functions?
- What's the best way to do stuff when Nestjs application loads?
- Should I put command bus between controller and domain service?
- Nestjs - should custom interceptors be organized in a module?
- Where should i put httpRequests in CQRS architecture using NestJs?
- Where to write common logic in Phoenix
- The best place to store logic in React app?
- ReactJs where to put reusable logic