Architecture question: how to programmatically throttle caller volumes in a service oriented architecture?

The best way to tackle this problem (in my opinion) is by using message oriented transport level (JMS, WebsphereMQ, MQMQ...).

The best way to tackle this problem (in my opinion) is by using message oriented transport level (JMS, WebsphereMQ, MQMQ...) In this case you have full control over handling the requests - and messages that can't be handled are just queued up. You can also easily add elements such as priorities, adding servers for scaling, etc. Any way - the service provider is responsible for supplying the agreed SLA.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.