Bounded Context

Hi there,

Please advice on the following:

Bounded-context (microservice):
While design process in bounded context (microservices) what is the best option to follow:

  • Calling a sub-process
  • Throwing message event
    image

What is the best practice in terms of bounded context (microservice).

Regards,

What specific behaviour are you trying to archive?

  1. Call activity is a blocking activity: in order move to the next activity after the call activity you have to complete the call activity’s sun process. The call activity will let you perform async activities and still wait for the total completion of the sub process. The call activity will share some scope/execution relationships with the parent.

  2. The message event allows you to trigger the sub process and not wait for the completion of the sub process. There is not shared scope/execution in the same way the call activity shares the scope. You will have to manually message the parent process if you have a “callback”. Message callbacks could be completed by external systems.

1 Like

@StephenOTT thanks for the guidance. It is much clearer now!

I will decompose the process to fit into microservices accordingly.

Regards,