Here’s the scenario:
Many users access an application (running on tomcat), the user’s data is segmented into multiple databases, say each db containing 1000 user’s data.
Now is it somehow possible to have 100s of tomcat servers running on ‘inexpensive’ PC class machines with each connecting to a single db, with user’s session getting passed to appropriate tomcat and becoming ‘Sticky’ there. Can have some sort of ‘gateway’ deciding which user goes where and doing the load-balancing appropriately.
Would make a great scalability solution 🙂
The way Juriy has already started on was mod_jk, can be found at the JK Mod site, which talks about load balancing.
Now, if you need Apache to send the user to a specific machine based on the user, then you just need to make sure that session-cookie(issued they first get there) doesn’t expire. Of course, what happens if they clear their session cookie?
From the sounds of it, you want to do something similar to database sharding. Is that more or less correct?