<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://andypardue.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Andy Pardue</title>
 <link>http://andypardue.sys-con.com/</link>
 <description>Latest News from Andy Pardue</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Sun, 29 Nov 2009 08:18:38 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Java Feature — Concurrent Queries</title>
 <link>http://andypardue.sys-con.com/node/313540</link>
 <description>Does this sound familiar? You have a domain object, perhaps for reporting purposes, that&#039;s built from a ton of JDBC queries  and it takes too long to load. Nothing else happens until this object is built, so it&#039;s become a bottleneck. Even worse, each of the queries is actually well tuned, so there isn&#039;t much to gain from modifying the queries themselves - there are just too many of them. You don&#039;t want to change (or can&#039;t change) your data model, so what can be done to alleviate this problem short of a major redesign? There are several options like caching, lazy loading, resource pooling. Another worthy option would be to implement a variation of the concurrent query pattern.&lt;p&gt;&lt;a href=&quot;http://andypardue.sys-con.com/node/313540&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 24 Dec 2006 22:00:00 EST</pubDate>
 <guid isPermaLink="true">http://andypardue.sys-con.com/node/313540</guid>
 <comments>http://andypardue.sys-con.com/node/313540#feedback</comments>
</item>
</channel>
</rss>
