web stats
Mirth Community - View Single Post - Mirth Connect 3.7.0 Released!
View Single Post
  #3  
Old 12-26-2018, 05:28 PM
narupley's Avatar
narupley narupley is online now
Mirth Employee
 
Join Date: Oct 2010
Posts: 7,126
narupley is on a distinguished road
Default

Quote:
Originally Posted by smealio View Post
Interesting.

As the architect at one of your clients I am strongly disappointed.

Not because of the functionality, I think that the new features are valuable and enjoy seeing the direction.

What I am disappointed about is that no more than 2 months ago, while implementing connect from ground up I attempted to put two connect instances in an active/active state behind a LB (this is how our legacy engine was implemented). When I realized I could not achieve FIFO in this setup, unlike our current engine BizTalk, I broached this topic with support and engineers.

Point blank, when asked if this would be supported in a future release so we could plan accordingly, we were told "this was not on the roadmap".

I feel like there is great disconnect amongst areas of consumer pipeline.
Perhaps there was a misunderstanding, or the rep you talked to was speaking to the strictly open-source side of things?

I know you already know this, but for others reading this I wanted to give some background. We have an Advanced Clustering commercial extension that adds a ton of functionality to Connect to better support multiple servers in a cluster. Things like an overhauled dashboard to show you all stats across all servers, deploying/starting/etc a channel will deploy/start it across all servers in the cluster, and more.

In 3.7 we added the Guarantee Message Order feature so that your interfaces can still be one-at-a-time and FIFO even when there are multiple servers running simultaneously.
__________________
Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

Nicholas Rupley
Work: 949-237-6069
Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


- How do I foo?
- You just bar.
Reply With Quote