<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Acid Reign</title>
<link>http://www.weblogic.sys-con.com/</link>
<description>Latest articles from Acid Reign</description>
<copyright>Copyright 2008 WEBLOGIC JOURNAL</copyright>
<lastBuildDate>Fri, 25 Jul 2008 05:47:00 GMT</lastBuildDate>
<generator>WEBLOGIC JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Is the Glass Half Full or Half Empty?</title>
<guid isPermaLink="true">http://www.weblogic.sys-con.com/read/185295.htm</guid><link>http://www.weblogic.sys-con.com/read/185295.htm</link>
<pubDate>Sat, 18 Feb 2006 10:30:00 GMT</pubDate>
<description>In this column over the years, I have spent a considerable amount of time talking about contention and locking in the database tier. At the end of the day, the endless conversations about scaling the application tier boil down to less than a bag of beans if a scaled application can&apos;t go any faster because the database has hit a limit.</description>

</item><item>
<title>Avoiding Middle-Aged Spread for Your WebLogic Infrastructure</title>
<guid isPermaLink="true">http://www.weblogic.sys-con.com/read/169376.htm</guid><link>http://www.weblogic.sys-con.com/read/169376.htm</link>
<pubDate>Thu, 26 Jan 2006 18:45:00 GMT</pubDate>
<description>I have been knocking around the computer industry for a while now, and I&apos;ve noticed some changes in my contemporaries and myself... For one thing, the buttons around the stomach of those old shirts that have eluded capture by my wife are looking a bit more strained than they did in the shirts&apos; heyday.</description>

</item><item>
<title>WebLogic Performance: Pursuit of Speed Isn&apos;t Everything</title>
<guid isPermaLink="true">http://www.weblogic.sys-con.com/read/138276.htm</guid><link>http://www.weblogic.sys-con.com/read/138276.htm</link>
<pubDate>Sat, 29 Oct 2005 12:15:00 GMT</pubDate>
<description>&apos;High performance&apos; is what everybody strives for when putting together a new system. Technical folk often spend hours hung up on the raw speed of their code, and a certain machismo can be derived from shaving milliseconds off that pesky transaction that is the latest pride and joy. Often, this time is not very well spent.</description>

</item><item>
<title>Defragment Your View of the World for a Quiet Life</title>
<guid isPermaLink="true">http://www.weblogic.sys-con.com/read/117495.htm</guid><link>http://www.weblogic.sys-con.com/read/117495.htm</link>
<pubDate>Mon, 08 Aug 2005 12:00:00 GMT</pubDate>
<description>The value of two phase commit transactions has always been that programmers can write applications that access data spread across multiple databases and be confident that any updates that are made will be consistently reflected in all of the databases, or none, at the end of the transaction.</description>

</item></channel></rss>