faster access to web site for special users

[architecture]

Hi

can anybody tell me the way, for having faster access to
a j2ee based web site, for a set of special users.

i mean can we let a set of users have faster access.

will it anyway help with access control lists.

thanks in advance

 

[DixieFlatline]

I am just brain storming out loud here...

I think that you can achieve this my first doing validation, using whatever method you like to use. Then perhaps a session or an entity bean that can check privilege of the user. Based on the privilege, you can instantiate different session or entity beans ( sessions if you have time to implement a full session-entity facade pattern). Have different database pools, for example, privilege pool with 50 connections and commoner pool with 50 connections. Have your different entities beans access the db using the different pools. Therefore if I am a privileged user, I would have the privileged version of getAccountBalance session bean instantiated, which accesses the privilege version of the Account entity bean which accesses the privileged db connection pool. Considering that there would be a smaller number of privileged user sharing a connection pool of same size as common user. A privilege user would have much faster access to data. Aside from just playing with db connection number, you can also, play with the ratio of cached ejbs for the 2 different classes. I think this should work... of course, you can also look at request forwarding and load balance off 2 web servers, but that is just boring.

Dix

 

[architecture]

thanks for the reply. but i still have a doubt in this. the thing is in this case the regular users are in miillions and
the priorotised users like admin users are may be at the most in hundreds. in this way are we not deliberately reducing the access speed for the rest of the users. i mean could there be any way, where keeping the rest of the users access speed untouched, we can achieve the required access speed to the previleged ones.

thanks

 

[DixieFlatline]

hummm... the 50/50 split is just an example. Let's just say you have 200 concurrent connection to your db right now and you have thousands of concurrent users at peak times. I would assume, if it is a data intensive application, that most of the time will be spent waiting for connections... In that sense, what if you just add an extra 10 or 20 connections and use them exclusively for admins... I think that unless you increase the overall performance of every component, there is no way to achieve what you want. Without knowing you system, I am just assuming bottle neck at db connectivity, since my experience tells me that is usually where it happens. Maybe your best bet is to profile your system and find the bottle neck and then try to address the issue. It is rather difficult to scale when you don't know which part needs scaling. If you have a centralized non replicated db, the db will probably will be you slowest part and there aren't much you can do other than to increase its performance. Once that is done, many steps can be taken to increase over performance for admins. Replicate base and archive data into a new db and use db link to access the main db for updates. Anyway, I have blabbed enough. Good luck in you design and implementation.

Dix