E
eJAYBee
I am being told that even when point A to point B communication,
originating at point A, is synchronous, send a message to B wait for B
to finish processing and send a tagged(to corelate the response to the
request) message back asynchronously via another Q will improve the
response time and scalability during peak volume vis-a-vis a
synchronous API call between A and B. A being a servlet B being an
application server hosted on a container. Keep in mind that this
application cannot live with the fact that there is a possibility that
the response may never come back (timeout). The expected response time
during average load is <2sec. Peak load 110 transactions per second.
Response time of 5 secs during peak load is unacceptable. Clustering is
certainly a consideration. Any opinion, pointers, etc. is welcome.
Have a wonderful weekend!!
originating at point A, is synchronous, send a message to B wait for B
to finish processing and send a tagged(to corelate the response to the
request) message back asynchronously via another Q will improve the
response time and scalability during peak volume vis-a-vis a
synchronous API call between A and B. A being a servlet B being an
application server hosted on a container. Keep in mind that this
application cannot live with the fact that there is a possibility that
the response may never come back (timeout). The expected response time
during average load is <2sec. Peak load 110 transactions per second.
Response time of 5 secs during peak load is unacceptable. Clustering is
certainly a consideration. Any opinion, pointers, etc. is welcome.
Have a wonderful weekend!!