Adam Bien's Weblog
What is the difference between pooling and caching?
The difference is simple. Pooling is appropriate if you don't care about the internal state of a particular class / type. Pooling is mainly motivated by technical reasons like performance, latency or memory optimizations.
Caching is all about state. You want to retain the state for performance reasons and store (cache) it in objects between calls. So instead loading the state from the database in every request, you could cache the data between requests in valid objects.
Posted at 11:03AM Jan 11, 2010 by Adam Bien in Real World Java EE Patterns - Rethinking Best Practices | Comments[1] | Views/Hits: 1720
*NEW* Workshop: "Real World Java EE 6/7 Bootstrap" and book: Real World Java EE Night Hacks--Dissecting the Business Tier Tweet Follow @AdamBien
Since I'm interested in db connection state (specifying validate query, so connection gets validated before being returned to the caller), is my db connection pool then actually connection cache?
Posted by Stevo Slavic on January 22, 2010 at 01:03 AM CET #