Database Connections vs. Users Onsite
 

Someone asked me the other day about DB connections and users* and they interpreted that per user equalled a database connection. This was a discussion in relation to a server with how many DB connections for a vb forum.

My understanding* and hopefully server techs can elaborate or correct as necessary* is that they really have nothing to do with one another in relation to say... if your DB connections are set at 300* this does not mean you can only have 300 users on your forum at once.

My understanding* is that only something like PostgreSQL that allows one connection from the frontend to database at a time* then this would apply* but not with MySQL and other database types where connection pooling is utilised.

My understanding that the connections are short bursts only to load the frontend data when asked* or write to the database* thus you could actually have 2000 users online at once and unless all 2000 simultaneously hit a button to retrieve or post something to the database all at once* then things would function as normal. Even if all 2000 did* then connection pooling would apply for same pages being read at that instance* and some may simply experience a short delay in the data being loaded or written* ie. a few extra seconds.

I am not sure how to explain this accurately* but would love a basic explanation if someone could do so.

Is my interpretation and understanding of this correct or not?