This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hi! Thanks for the reply. But my question has more to do with the performance as per the documents. Its says need bettr performance for travel agent application. If I use HTTP session (servlet) for both Web client and travel agent swing application, then how does the peformance differ? On the other hand, if I use SFSB for storing session then both can use it. Plus, Swing can call EJB directly thus reducing network traffic and improving performance. Pls advice?
sankha subhra das
Joined: Jun 24, 2003
Bharat, precisely thats where u need to wear ur "architectural" cap and make a judicious choice. Yes travel agents will be the core of the business, hence the system should be fast/available to agents at all times. You mentioned, "If I use HTTP session (servlet) for both Web client and travel agent swing application, then how does the peformance differ?" Take note first that http session can be used with web components only and NOT swing components. Now for the typical customer, you have a choice of using httpsession or SSB.There's plenty of articles on the internet discussing/comparing the two. As an architect, u need to think if httpsession will suffice for the amount of data to be stored in session. Also remember httpsession works best for storing small amounts of data like user navigation, preferences etc. I have used httpsession for my customer interface and provided justification for the same. yes ur right when ur say that the use of SFSB will suffice both the actors' needs. Do u see any other choice than using swing components to talk to EJB's directly ? u might have ur own session management handling (like sending data back and forth between requests) or store it as a cache in agent's system. now u hafta figure out the performance impact between client side caching vis-a-vis server side caching thru SFSB's. again u hafta get back and see if the hardware provided will allow u this at the client without the need for extra caching servers. as a general rule, performance wise its faster for swing components to access business tier directly and web clients to use httpsession over SFSB's for most business processes. As I said before, there is nothing wrong or right as far as architecture is concerned, it all depends on what assumptions u make and how best u fulfil the requirements given the hardware constraints.
Just to add. I have read somewhere sometime back that SFSBs are not good in clustering environment .
Joined: Jul 14, 2005
Thanks Sankha. It was helpful. I wanted to discuss some design choices in my current work area. Thought of discussing it with you if you interested. Kindly e-mail me at firstname.lastname@example.org, and i can take it offline.