Is Connection Pooling still necessary?

I'm developing a webapp that is going to be making frequent DB operations. I know that DB connections are expensive and that developers pool connections to prevent the overhead of frequent instantiation. Is this design pattern still necessary? I ask because I vaguely recall skimming over an

Re: Is Connection Pooling still necessary?

Jonathan Mast wrote: I'm developing a webapp that is going to be making frequent DB operations. I know that DB connections are expensive and that developers pool connections to prevent the overhead of frequent instantiation. Is this design pattern still necessary? I ask because I vaguely

Re: Is Connection Pooling still necessary?

OK, but isn't there all kinds of special configuration required? The only part of J2EE I'm using is JSP, no Servlets, no JNDI, just POJOs (J2SE) doing the database work. Will Tomcat still automagically handle the pooling for me? Sounds a little too good to be true, to me. But I've never done

Re: Is Connection Pooling still necessary?

Pooling still makes sense although in modern servlet containers it's provided. Outside the JVM, there's the overhead of making the connection and authenticating that can eat up significant amounts of time in busy sites with large numbers of queries to the db. Those costs are completely

RE: Is Connection Pooling still necessary?

Jonathan Mast wrote: I know that DB connections are expensive and that developers pool connections to prevent the overhead of frequent instantiation. Is this design pattern still necessary? I ask because I vaguely recall skimming over an article that stated that this design pattern is not

Re: Is Connection Pooling still necessary?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan, Jonathan Mast wrote: | OK, but isn't there all kinds of special configuration required? The only | part of J2EE I'm using is JSP, no Servlets, no JNDI, just POJOs (J2SE) doing | the database work. Will Tomcat still automagically handle

Re: Is Connection Pooling still necessary?

David kerber wrote: Jonathan Mast wrote: I'm developing a webapp that is going to be making frequent DB operations. I know that DB connections are expensive and that developers pool connections to prevent the overhead of frequent instantiation. Is this design pattern still necessary? I ask

Re: Is Connection Pooling still necessary?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, David kerber wrote: | David kerber wrote: | Looking at these other posts, and the reference Charles posted, it's | apparent that I've been getting away without using pooling, even though | I though I was using it... Some drivers actually do