Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

suggest some design patterns for complex business scenario  RSS feed

 
Shail Bade
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am included in a team which is designing a big user interaction. On a high level it starts with a UI where user enters some information and this follows to 4-5 screens. Between these user interactions, there will be around 8-10 webservice calls to external systems to fetch data from SORs for some of user entries/selection. Half the interaction is a question and answer based where the flow goes to multiple routes. After user interaction is done the systems goes to process this information and enters the second background flow which will continue to different conditions and will include another 30-40 webservice calls at different steps. This is followed by another UI interaction. However, we are planning to move this to be in first part so that all UI interaction gets over in one shot and system them starts processing offline.

I would want suggestion on design pattern that can help manage continuity, exception handling for these many web service calls. Plus some mechanism for the flow to recover in case of temporary error/service timeouts. I can use queueing here.

Wanted to check if somebody has some good ideas here.

 
Abhay Agarwal
Ranch Hand
Posts: 1376
Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to Javaranch !!

On a high level it starts with a UI where user enters some information and this follows to 4-5 screens.

You can use Spring MVC or Spring Web Flow

Between these user interactions, there will be around 8-10 webservice calls to external systems to fetch data from SORs for some of user entries/selection.

you may use any ESB framework [ Mule, ServiceMix etc] to handle multiple web services call.

After user interaction is done the systems goes to process this information and enters the second background flow which will continue to different conditions and will include another 30-40 webservice calls at different steps. This is followed by another UI interaction. However, we are planning to move this to be in first part so that all UI interaction gets over in one shot and system them starts processing offline.

you can use Spring Batch to perform background work.

I would want suggestion on design pattern that can help manage continuity, exception handling for these many web service calls. Plus some mechanism for the flow to recover in case of temporary error/service timeouts.

Normal search on Google can guide you to design/learn some good exception handling.
http://www.onjava.com/pub/a/onjava/2003/11/19/exceptions.html
http://codebuild.blogspot.com/2012/01/15-best-practices-about-exception.html
http://today.java.net/article/2006/04/04/exception-handling-antipatterns


 
Shail Bade
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for reply...Let me do some research.
 
Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!