I am quite new to DDD, but I am currently working on a system which has a payroll element to it. I have a requirement to send payslips to an external system when they are created. Currently the payslip process is all in the existing legacy code, but I was thinking that it might be a good chance to move some code into a bounded context that has recently been created for payroll to slowly migrate the legacy code to. The system isn't distributed so everything all runs in one process.

My thoughts were to make an application service which would orchestrate calling an infrastructure service to send the data to the external system and then update the status of the payslip. This would be called from the legacy code. Is an infrastructure service the right thing for this integration, or is the whole thing a design smell?

New contributor
Steven Brookes is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

Your Answer

Steven Brookes is a new contributor. Be nice, and check out our Code of Conduct.
 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.