Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Login Module Implementation - Around 20k users for the application

 
Vaibhav G Garg
Ranch Hand
Posts: 143
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are working on a web application which will be having 20,000+ end users. We have to build up the login module for this application. Please suggest the best ways to implement the login module so that there are no performance issues during high load.

What are the best practices we need to follow for the same?

Also, how to control the concurrency and transactions for the same?
 
Winston Gutkowski
Bartender
Pie
Posts: 10427
63
Eclipse IDE Hibernate Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Vaibhav G Garg wrote:Please suggest the best ways to implement the login module so that there are no performance issues during high load.

The same way that you'd write any other module that's likely to be used frequently and needs access to shared data. I'm not quite sure why you'd think a login would be particularly different.

What are the best practices we need to follow for the same?

What, specifically for a login method? Most of those will have to do with security rather than performance (eg, using https rather than straight http).

Also, how to control the concurrency and transactions for the same?

I'm afraid that's far too broad a question to be answered in a forum like this. One basic premise is that you keep all transactions that require exclusive access as short as possible though.

Perhaps you could ask a more specific question; then we might be better able to help you.

Winston
 
Jeff Verdegan
Bartender
Posts: 6109
6
Android IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'll point out that a login module is unlikely to be a performance bottleneck. If I login once for every 10 normal actions I perform, that means that 1/11th of your traffic at any given time will be due to login requests. Most sites I use, it's even more skewed than that, like one login for every 20 or 100 or 1000 other actions.

So don't worry about login performance unless and until it becomes a problem. First make it work, and if you're going to look at performance, look at it for stuff your users do once they're logged in, as that's likely to be called much more often.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic