|
Connection Pooling
A technique that is used in industry for maintaining as few DB connections as possible is connection pooling. I program primarily in Java, so that is what I am basing this suggestion off of.
If you have a system that requires many small transactions to a database, very few of them are actually run simultaneously. You can have a pool of seemingly very few connections that get shared throughout the application. You have to be very careful to release the connections back to the pool EVERY time, especially when something fails. Otherwise you'll run out of available connections.
Most (all?) of the major web-based applications that are running out there use connection pooling rather than having dedicated connections for each transaction.
__________________
"Memo to myself, do the dumb things I gotta do. Touch the puppet head."
-TMBG
|