We are getting closer to our license thread count for prod and are looking at additional quite a few threads to support a new application that will go live in Fall 2022. We are requesting an increase in our licensed thread count but also looking at areas where we can trim unneeded thread connections.
What are folks doing when they get their inbound ADT (we get from Epic) that goes to multiple threads in that same process that then connect to a listening thread in multiple processes on the ADT site? example thread is sent to 5 client tcp threads that than have a server tcp thread in different processes on the site. Every time we want to send data from that inbound ADT thread to different processes, we use 2 threads (client/server) for each processes that we want to send ADT to.
I have seen this same setup at other places I have worked at.
Sometime ago I tried playing around with the intra-site routing but that only works if routing to a different site.
I have tried testing routing directly to the inbound thread on each process and setting the inbound hread (setup as /dev/null file thread) so that each message routed to it is treated as inbound but have had the sending process crash in the test environment.
Appreciate any recommendations that others have done. I understand the need for client and server tcp threads especially for connecting with external systems but when it is used purely for routing to multiple inbound threads on multiple processes, seems like there has to be a better way.