Skip to content

Instantly share code, notes, and snippets.

@jonbartels
Last active April 24, 2023 16:07
Show Gist options
  • Save jonbartels/675b164000bfedd29a0a5f2d841d92fa to your computer and use it in GitHub Desktop.
Save jonbartels/675b164000bfedd29a0a5f2d841d92fa to your computer and use it in GitHub Desktop.
Mirth Connect Source Queues are Evil

Source queues in MC are Evil

I was called out on Slack this week for my long standing assertion that "source queues are evil". I will cede that this is said somewhat jokingly, but it is based in fact. I have never been able to quickly explain my position so I wrote this gist to organize my thoughts.

Brief Listing

  • source queues are hard to manage compared to destination queues
  • Destination queues will retry if the downstream channel is down for some reason.
  • Destination queues allow the engineer to add or reduce threads to process the message volume at the desired rate
  • source queues trigger message recovery which is slow
  • source queues cannot send auto-generated responses for all message types

Gory Details

What is Message Recovery

How can I shift source queues to destination queues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment