The following considerations should be taken into account while implementing this pattern:

• Increase in Complexity: Decomposing an application in to Microservices, introduces the complexity of managing these services discretely. Also, the communication between the processes becomes less deterministic as they are asynchronous by nature. It is important to account for the overheard in management effort while implementing this pattern.
• Poison messages: There is a chance that an instance of a Microservice in a pipeline fails to process a message pipe as it causes an unexpected fault. In this case, the Microservice will retry processing this message for few times and then discards it. These messages usually end up in a dead letter queue which then needs to be handled separately.
• Transactions: Incase an end-to-end processing of a pipeline fails in between, the state changes which are committed as a part of the current transaction must be reversed to preserve the integrity of the system.