The ThoughtWorks tech radar once talked about choosing Choreography over Orchestration. I'll try to explain this using real world examples and touch upon some other points of service orientation along the way.
first create her record in employee master e.g. peoplesoft also need to create it in corporate directory, email system, time & expense, skills master based on role, office - need to add the new joinee to certain groups different systems may need different parts of employee data 4
would just publish the event on a queue, and the other system would look at the published employee and create a copy for itself with a subset of the info e.g. corporate directory doesn't care if you are a dev or manager but skillsMaster does. email system doesn't care about salary but payroll does. this is how a choreo approach would look like 7
programming? or pub-sub? in a sense yes, it is sort of a distributed observer but that is not all. we are doing this to achieve decoupling at several levels availalbity clearer boundaries help the cause of autonomy remember: it is possible to get it wrong with events also. what you publish is important an event describes "what happened", not "what should happen" - that is a request/command message,document 8