I'm building a web application login module. Whenever a user login, the application would access the database SEVERAL times to pick up information for authentication. An average of ~60 users would use the system.
I'm a bit worry about the data access portion. If I would to get and close a database connection on each login, is it better off if I just keep a database connection which would be open whenever the server is up, just to handle this kind of request? Meaning I don't close it.
Connection pooling might be another way but my argument is that I only need 1 connection for that purpose, so pooling doesn't serve much purpose there.