In our sample scene, we have a business process in the Regulatory Affairs department, which is about the documents validation process. This process is actually a service composition in the form of service choreography. Remember, in choreography, there is no director or controller for the execution of all the services, but they are executed sequentially in a set order to achieve a business process.

Our sample process starts from the DB Monitor background service, which sends one message or one service call for each expiring document in its validation process. It sends out the notification through our service Document Validity Notify, which then calls the Document Submitter service to pass on the documents for their renewals (for example), and after some time (required to process the renewal request forms), we get the renewed document back via one of the B2B services Passport Receiver (for example, to receive the specific document, that is, Passport). The Passport Receiver service will then call the Update HR Document (UploadSingleFile) service to pass on the new document to the HR department to save a copy in their database:

This concludes our service composition as a choreography. Since it's not a workflow, we do not need to explicitly close the status of the business process and there is no need to update the process starter.