This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Your connection pooling, and efficient use of connections is an absolutely critical part of your entire architecture. Working with WebSphere, I always prefer to defer to WebSphere connection pooling. Why? Bias perhaps, but I like the idea of offloading this important work to the server provider. I'm assuming the server vendor has put more work into making their pooling services more reliable and robust than the ones that are managed and maintained within a give web app or ejb app. Plus, if something goes wrong, I've got the vendor's 'throat to choke.' If something goes wrong with Hibernate connection pooling, whose throat do you go for? With IBM, there's always a sales guy with a sore neck willing to offer support.
Luciano A. Pozzo
Joined: Jun 20, 2005
I agree, but let us suppose that I am using JBoss and I don't have support. So, there is a benefit (maybe performance, manageability, etc)? Or is the same in both cases?
Cameron Wallace McKenzie
author and cow tipper
Actually, I've always found that JBoss had the best paid support out there, but that's another story.
Beyond just trusting the vendor, I'm not sure of any definitive benefits. Maybe someone else can pipe in? Even my justification is more based on "Fear, Uncertainty and Doubt" as opposed to any real or calculated metrics or comparisons.