<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jdbi on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/jdbi/</link>
    <description>Recent content in Jdbi on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/jdbi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Java Database Access Libraries: JDBI 3 vs MyBatis vs jOOQ — Self-Hosted Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-07-29-java-database-access-libraries-jdbi3-mybatis-jooq-guide/</link>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-29-java-database-access-libraries-jdbi3-mybatis-jooq-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;SQL is the universal language of data, yet Java&amp;rsquo;s native JDBC API is notoriously verbose — 10 lines of boilerplate just to execute a single query. The Java ecosystem has responded with three distinct approaches to database access: &lt;strong&gt;JDBI 3&lt;/strong&gt; (fluent JDBC wrapper), &lt;strong&gt;MyBatis&lt;/strong&gt; (SQL mapping framework), and &lt;strong&gt;jOOQ&lt;/strong&gt; (type-safe SQL builder with code generation). This guide compares all three with production-grade code examples and performance benchmarks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
