<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Connection-Pool on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/connection-pool/</link>
    <description>Recent content in Connection-Pool on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/connection-pool/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java Connection Pool Libraries in 2026: HikariCP vs Commons DBCP vs Tomcat JDBC</title>
      <link>https://www.pistack.xyz/posts/2026-08-31-java-connection-pools-hikaricp-commons-dbcp-tomcat-jdbc/</link>
      <pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-31-java-connection-pools-hikaricp-commons-dbcp-tomcat-jdbc/</guid>
      <description>&lt;p&gt;A single misconfigured connection pool can turn a 5-millisecond database query into a 40-second pileup under load. Every Java application that touches a relational database eventually needs one, and the choice between HikariCP, Apache Commons DBCP 2, and Tomcat JDBC is one of the most consequential decisions you can make for your application&amp;rsquo;s latency curve — yet most teams pick whichever pool their framework happens to bundle. This guide compares all three pools with live GitHub data, real configuration examples, and the performance trade-offs you will actually feel in production.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
