So we'll also now discuss what I was showing before where this application premium process or a process manager or saga is being used to generate steps. on the steps that are taken, the commands that are accepted and processed are emitting events, and the events are being consumed by the application premium process. A process manager is known as an orchestrator, so this is process orchestration. Notice that the message bus is still here, but rather than each of the risk rate and underwriting having to translate the incoming event into a command that it understands, what happens instead is that the application premium process does the translation for it. So notice that on the message bus we have application submitted, and in the premium process the application submitted is translated to assess risk on behalf of the risk-bounded context, and therefore, rather than the risk context having to translate that through an adapter, it simply receives the assess risk command, processes that, and then emits the risk assessed. And you can see how that event translation continues to occur. This is actually the same process that you saw before through choreography, but with the benefit of having an orchestrator take care of some of the heavy lifting and routing on behalf of the overall system.