- The document discusses using microservices and event-driven architecture together with orchestration. It notes that while events allow for loose coupling, tracking logical flows across services can become difficult. - An order handling example is presented to illustrate challenges like a payment service needing to know all possible events that could trigger a payment. This calls for introducing an order service to handle event-command transformation and orchestration across services. - The document argues that modern lightweight workflow engines can be embedded within microservices to enable orchestration without introducing a centralized point of control. This allows logical flows to be modeled and changes to be made without affecting individual services.