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.
Hello ranchers, I had an argument with my friend about a design they chose. They have a "centralized" servlet that receives requests and just delegates them to the other servlets. Now the other servlets do the processing and return. He is saying that this would allow "container independent" load balancing, in case we want to distribute the load via this servlet. I told him that this is far from being the way u do load balancing (after all, u can just toggle some XML fields, and let the container do it for u automatically, no need to change the code...) and I told him that this is just adding overhead (calling a servlet instead of a simple POJO for the business logic/we r not using EJBs). Now assuming we don't take in consideration that the business logic should be separated from the "servlet" related code, or we just assume that the second layer servlets (those that process the requests dispatched to them by the MAIN controller servlet) also delegate the call to POJOs for business logic; IS there any advantage of Having this kinda of chain of servlets ? (not filters) ?? Do u guys have any good/bad arguments for/against it? Please advice us, we really need other people's view! Thanks for your time
Joined: Dec 30, 2003
Heh, No replies Come on guys, Shoot, just any thoguhts :roll: