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.
Ok, here is the criteria: Clients must access a database via an applet through a Web Server from the Internet(outside world) Database resides on it's own Server Use RMI and JDBC for Database to Client Coomunication Here is the problem: Let's say I anticipate 5000 clients accessing, reading, and writing to the database at any given time. Here are the questions: Is there a way to disign this system so that the sending and recieveing of information is handed off to another Server freeing the Web Server for other tasks? Can the one instance of the DriverManager handle that kind of workload? Is there a better design than simply Three-Tier for this kind of operation? I am currently hunding the Internet for design and architecture ideas, so any from you wonderful people here would be great. Thanks alot