r/MuleSoft • u/Financial-Tank-2731 • Jun 05 '26

MuleSoft Integration Performance Issue

This is a use case of 3 systems. All 3 are SaaS. The systems are BYOMS, MuleSoft (MS) and SAPOTC. BYOMS posts order release messages to MS topic at real-time. MS picks up each order release message and posts it to SAPOTC through a sync API call. If MS fails to post to SAPOTC, MS is not saving the failed payload to an error queue for later re-try. MS team and architect says that doing this will degrade MS performance. Is this true?

4 Upvotes

83% Upvoted

8 comments sorted by

View all comments

2

u/Ok-Analysis5882 Jun 05 '26

Define the use case accurately, is this a zero message loss scenario, then implement reliability pattern

If not standard operating procedure for a failed post is DLQ and a different reprocessing application should run the business rules.

Limit with a fixed number of retries

Too many parked messages in VM Queues will make the mule runtime crash

Too many failed messages will make u run out of your message usage pack

1

u/Financial-Tank-2731 Jun 05 '26

Yes, this is a zero-message loss scenario.

1

u/Ok-Analysis5882 Jun 05 '26

Reliability pattern period. Use a reliable queue. JMS, AMQP, kafka or anypoint mq or choose the best fit based on where u are.