O
oljeg.popovic
Hello,
I have following scenario.
My web service is receiving package of messages (from 1 to 100) which I
have to distribute to other back-end web services, aggregate responses
and return them to client as one response.
I have read articles on MSDN At Your Service column but I still have
some doubts:
1. How to implement simultaneous calls to web service and return
aggregated responses?
2. Shall I use my own thread pool?
3. Is this architectural solution acceptable or shall I use total async
approach (MSMQ, Windows services, ..). In pick, I'm expecting about 100
packages (about 1000 messages) per second.
Thanks!
Regards,
Oljeg
I have following scenario.
My web service is receiving package of messages (from 1 to 100) which I
have to distribute to other back-end web services, aggregate responses
and return them to client as one response.
I have read articles on MSDN At Your Service column but I still have
some doubts:
1. How to implement simultaneous calls to web service and return
aggregated responses?
2. Shall I use my own thread pool?
3. Is this architectural solution acceptable or shall I use total async
approach (MSMQ, Windows services, ..). In pick, I'm expecting about 100
packages (about 1000 messages) per second.
Thanks!
Regards,
Oljeg