What's the best strategy to deploy my web system to large pool of users (using JBoss and Oracle DB)
Posted on 2003-03-31
We have developed our system using JBoss 3.0.4 (tomcat 4.1.12). We're using Oracle 8i database. We also interface information from other Oracle database using dblink (the Siebel and Peoplesoft applications which is stationed at different machines).
Now we need to roll out our system to 1,500 users. So, the concurrent access at one time can reach 1,500.
We have heard so far a lot of system encountered problem when they go life to large pool of users, for eg: connection limit reached, exceeded the cursor limits, web server crash, etc.
Is there anybody can guide me on the roll out strategy? (not from the business perspective, as we cannot control the number of users using the system at any time). Any info that can help to roll out smoothly, like the architecture, what kind of configurations needed to be made at JBoss as well as Oracle DB.
So far, is there anybody using JBoss and Oracle DB and the system has been rolled out to a few thousand users and the system still working fine? Can someone share the experience/learning points with me?
Somebody has proposed to me use 2 web server with standalone database. At the end of the mth, synchronize the data back to the centralised database. Not too sure is this strategy good, but the maintenance is high. Especially when you need to view the report of the data and if there are changes to some code values which are shared by all. The synchronization cost is high.
Our another problem is the machine issues. We can't afford high end machines.
Hope someone can help me. Thanks.