Multi-Threading Design Question for ASP.NET MVC 2

Question

I am working on a Travel related website and here is my high level architecture:

ASP.NET MVC 2 (Presentation Layer) 
Services Layer 
Repository Layer communicating with external J2EE Services

For a particular user search scenario, I need to call the J2EE service 4 to 5 times (independent operations), consolidate all responses into a single response and hand it over to the Controller to be able to present it to user.

What is the best way to handle this scenario? Should I use AsyncController feature of MVC 2 or implement some multi-threading logic in my Service layer?

Answer 1

Use Async controller

When should one use asynchronous controller in asp.net mvc 2?