The Orchestrator is a “process manager” that helps to address the complexity of SAGA pattern when we have a distributed. transaction that needs involving from many services. Instead of calling each other, services will call to the Orchestrator. We still need to store order status in the DB because the communication type here is “fire and forget” we can put the transaction on hold and resume it later on. You can have a central table to store the status of each step or choose to store the status in separate tables like my solution — it doesn’t matter.

For the 2nd point, you’re correct. However, at least using Orchestrator approach would help us to have a central place to manage processes and as a result it’s easy for maintaining.