<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:feedpress="https://feed.press/xmlns" xmlns:podcast="https://podcastindex.org/namespace/1.0" version="2.0">
  <!-- Source: https://feeds.dzone.com/home -->
  <channel>
    <feedpress:locale>en</feedpress:locale>
    <atom:link rel="self" href="https://siftrss.com/f/XXPJxjxNQe"/>
    <atom:link rel="hub" href="https://feedpress.superfeedr.com/"/>
    <title>DZone.com Feed</title>
    <link>https://siftrss.com/f/XXPJxjxNQe</link>
    <description>Recent posts on DZone.com</description>
    <item>
      <title>One Database, Two Models: Building AI-Friendly Java Applications With MySQL JSON Duality Views</title>
      <link>https://dzone.com/articles/mysql-json-duality-views</link>
      <description><![CDATA[<p>MySQL can now hand your application a complete JSON document, such as an order with its customer and line items, while the data stays in normal relational tables. You can even send the document back, and MySQL updates the right rows. I built a small Java app to see how far that goes. Reading got much simpler. Writing works too, but it comes with a few sharp edges you should know about before you use it.</p>
<h2>Four Tables, One Screen</h2>
<p>Picture a support screen for a small online shop. When a customer calls, the agent needs the order's customer, items, prices, and status in one place.</p>]]></description>
      <pubDate>Mon, 19 Oct 2026 14:00:00 GMT</pubDate>
      <guid isPermaLink="false">https://dzone.com/articles/3693038</guid>
      <media:thumbnail url="https://dz2cdn1.dzone.com/thumbnail?fid=19238768&amp;w=600"/>
      <dc:creator>A N M Bazlur Rahman</dc:creator>
    </item>
  </channel>
</rss>
