The following considerations should be applied while using this pattern:

• Coordinate only: Sagas are designed to coordinate the message flow. They make decisions through business logic. The actual work is delegated to the Microservices using the messages.
• Message starting the Saga: There might be more than one message that can start the saga.
• Message order: A delay in service response may result in messages arriving out of order. So, design the saga with fallacies of distributed computing in mind.