Service Design
I have 3 services that im trying to figure out how they should interact at a DI level.
1) a scheduling service that fires an event at a given time. this event is of predetermined types (Reminder, Send a message, etc).
2) an approval system for communications. User1 creates a communication, user2,user3,user4 vote to approve/deny/modify the communication.
3) a notification (sending) service that transmits the communication/ releases it to other users to view.
the most basic flow would be Api call to submit the communication=> Approval service (wait for approvals) => Schedule Service (after approved, when should this happen) => Sending Service (when the schedule trigger fires off).
how do i resolve the dependency injection for the various services? Does the Sending service only require the Schedule service, which in turn only requires the Approval service?
and what is the best manner to chain these together, or am i better off redesigning in a different schema?
In the current design i am running the Scheduling Service as a singleton, the approval service is likely scoped, and the sending service should be transient right? this raises the issue that the approval service cannot access the Scheduling service through DI because of the longer lifecycle. Looking for any advice on if im off base here.
TIA!
1) a scheduling service that fires an event at a given time. this event is of predetermined types (Reminder, Send a message, etc).
2) an approval system for communications. User1 creates a communication, user2,user3,user4 vote to approve/deny/modify the communication.
3) a notification (sending) service that transmits the communication/ releases it to other users to view.
the most basic flow would be Api call to submit the communication=> Approval service (wait for approvals) => Schedule Service (after approved, when should this happen) => Sending Service (when the schedule trigger fires off).
how do i resolve the dependency injection for the various services? Does the Sending service only require the Schedule service, which in turn only requires the Approval service?
and what is the best manner to chain these together, or am i better off redesigning in a different schema?
In the current design i am running the Scheduling Service as a singleton, the approval service is likely scoped, and the sending service should be transient right? this raises the issue that the approval service cannot access the Scheduling service through DI because of the longer lifecycle. Looking for any advice on if im off base here.
TIA!
