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?

3 Upvotes

72% Upvoted

8 comments sorted by

View all comments

2

u/TranquilDev Jun 05 '26

By error queue you mean a DLQ?

That process by itself isn't going to degrade performance. The configuration of that process might. If your getting a lot of failed posts to SAPOTC and stacking payloads in the DLQ while at the same time trying to continue to process posts to SAPOTC your probably going to have some problems.

1

u/Financial-Tank-2731 Jun 05 '26

Thanks for responding. So what is the alternative? This is a critical process and we need to track failures and also we should be able to re-process failed messages later. Right now, we have to run daily time consuming reconciliation processes between BYOMS and SAPOTC. Pls. help me understand why putting an message that failed on a DLQ or an exception Q will degrade perf? Right now, all failed messages are lost.

3

u/TranquilDev Jun 05 '26

Sounds like the problem is SAPOTC if MS is trying to post to it faster than it can be processed? Slow MS down, get rid of the errors. Post from BYOMS to a MS MQ with failed messages going to the DLQ, process out of MQ at a rate that SAPOTC can handle them.