<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ feed</description>
    <item>
      <title>30+ Updates per Second per Account: Uber Scales Ledger Processing with Batching</title>
      <link>https://www.infoq.com/news/2026/06/uber-payment-batching-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/uber-payment-batching-system/en/headerimage/generatedHeaderImage-1779570527807.jpg"/&gt;&lt;p&gt;Uber introduced a high-throughput financial ledger processing system designed to handle hot account write contention at scale. Using 250ms batching, Redis coordination, and optimistic atomic updates, the system supports 30+ updates per second per account while preserving consistency and auditability, reducing multi-hour processing pipelines to minutes in its distributed accounting infrastructure.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>HotSpot</category>
      <category>Event Driven Architecture</category>
      <category>Low Latency</category>
      <category>payment</category>
      <category>Transactions Processing</category>
      <category>Consistency</category>
      <category>Optimization</category>
      <category>Event Stream Processing</category>
      <category>Financial Applications</category>
      <category>Batch Processing</category>
      <category>Performance</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 14:02:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/uber-payment-batching-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-04T14:02:00Z</dc:date>
      <dc:identifier>/news/2026/06/uber-payment-batching-system/en</dc:identifier>
    </item>
    <item>
      <title>How a Culture of Data-Driven Conversations Can Support Platform Engineering</title>
      <link>https://www.infoq.com/news/2026/06/data-driven-platform-engineering/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/data-driven-platform-engineering/en/headerimage/generatedHeaderImage-1780255652688.jpg"/&gt;&lt;p&gt;To provide SRE as a service, a team built a center of excellence, introducing Federated SREs and roles like production manager and technical tribe lead. They created a culture of data-driven conversations where SLOs and SLAs were democratised. Surviving growing cognitive load meant continuously simplifying architecture and embedding sovereignty and resilience into platform design decisions.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Value &amp; Metrics</category>
      <category>Platform Engineering</category>
      <category>InfoQ Dev Summit Munich 2025</category>
      <category>QCon Software Development Conference</category>
      <category>Resilience</category>
      <category>Platforms</category>
      <category>Metrics</category>
      <category>Cloud</category>
      <category>Site Reliability Engineering</category>
      <category>Culture &amp; Methods</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 11:54:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/data-driven-platform-engineering/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-06-04T11:54:00Z</dc:date>
      <dc:identifier>/news/2026/06/data-driven-platform-engineering/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Architecting a Centralized Platform for Data Deletion at Netflix</title>
      <link>https://www.infoq.com/presentations/architecting-deletion-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/presentations/architecting-deletion-system/en/mediumimage/medium-1779869686290.jpg"/&gt;&lt;p&gt;The speakers discuss the architectural challenges of executing safe data deletion across distributed datastores. Balancing durability, availability &amp;  correctness, they explain how to orchestrate multi-system deletion propagation without impacting live traffic. They share lessons on controlling tombstone accumulation, building continuous audit loops, and gaining trust with a centralized platform.&lt;/p&gt; &lt;i&gt;By Vidhya Arvind, Shawn Liu&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>Platform Engineering</category>
      <category>QCon San Francisco 2025</category>
      <category>Performance &amp; Scalability</category>
      <category>Data</category>
      <category>Reliability</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Thu, 04 Jun 2026 10:26:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/architecting-deletion-system/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Vidhya Arvind, Shawn Liu</dc:creator>
      <dc:date>2026-06-04T10:26:00Z</dc:date>
      <dc:identifier>/presentations/architecting-deletion-system/en</dc:identifier>
    </item>
    <item>
      <title>Article: Architectural Change Cases: A Practical Tool for Evolutionary Architectures</title>
      <link>https://www.infoq.com/articles/architectural-change-cases/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/articles/architectural-change-cases/en/headerimage/architectural-change-cases-header-1780316814045.jpg"/&gt;&lt;p&gt;Architectural change cases extend architecture decision record (ADR) thinking by evaluating how decisions may evolve over time. Change cases expose hidden assumptions and help teams estimate the reversibility and cost of change.&lt;/p&gt; &lt;i&gt;By Pierre Pureur, Kurt Bittner&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>Architecture Documentation</category>
      <category>Architecture Evaluation</category>
      <category>Architecture Decision Records</category>
      <category>Evolutionary Architecture</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 04 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/architectural-change-cases/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Pierre Pureur, Kurt Bittner</dc:creator>
      <dc:date>2026-06-04T09:00:00Z</dc:date>
      <dc:identifier>/articles/architectural-change-cases/en</dc:identifier>
    </item>
    <item>
      <title>AWS Replaces Fat-Tree Data Center Networks with Random Graph Theory, Cutting Routers by 69%</title>
      <link>https://www.infoq.com/news/2026/06/aws-random-graph-data-center/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/aws-random-graph-data-center/en/headerimage/generatedHeaderImage-1780475849954.jpg"/&gt;&lt;p&gt;AWS disclosed that Resilient Network Graphs, a flat network architecture based on quasi-random graph theory, is now the default for most new data center builds. The design replaces fat-tree hierarchies with direct ToR-to-ToR mesh connections using passive optical ShuffleBoxes, cutting routers by 69%, boosting throughput by 33%, and reducing network power consumption by 40%.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Amazon Web Services</category>
      <category>AWS</category>
      <category>Infrastructure</category>
      <category>Deployment / Datacenter</category>
      <category>Cloud</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 08:25:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/aws-random-graph-data-center/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-06-04T08:25:00Z</dc:date>
      <dc:identifier>/news/2026/06/aws-random-graph-data-center/en</dc:identifier>
    </item>
    <item>
      <title>Next.js 16.2: 400% Faster Dev Startup, Faster Rendering, and Deeper Tooling for AI Agents</title>
      <link>https://www.infoq.com/news/2026/06/nextjs-6-2/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Vercel has released Next.js 16.2, featuring performance enhancements that make development startup 400% faster and rendering up to 60% quicker. The update includes AI-assisted development tools, improved Turbopack efficiency, and better error reporting. Migration from Next.js 15 is supported, and compatibility is set for Node.js 20.9 and TypeScript 5.1 or newer.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Next.js</category>
      <category>React</category>
      <category>JavaScript</category>
      <category>Web Development</category>
      <category>TypeScript</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 04 Jun 2026 06:47:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/nextjs-6-2/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-04T06:47:00Z</dc:date>
      <dc:identifier>/news/2026/06/nextjs-6-2/en</dc:identifier>
    </item>
    <item>
      <title>Inside Google’s System for Coordinated A/B Testing Across Its Global Service Fleet</title>
      <link>https://www.infoq.com/news/2026/06/google-fleet-ab-experimentation/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/google-fleet-ab-experimentation/en/headerimage/generatedHeaderImage-1779569949510.jpg"/&gt;&lt;p&gt;Google has shared details of its fleet wide large scale A/B experimentation system designed to standardize experiment assignment, exposure logging, and configuration propagation across distributed services. The approach enables consistent measurement across products, reduces experiment conflicts, and improves reliability of data driven decision making at scale.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Data-Driven Decision Making Series</category>
      <category>Infrastructure</category>
      <category>Feature Toggle</category>
      <category>Platforms</category>
      <category>Systems Thinking</category>
      <category>Logging</category>
      <category>User Experience</category>
      <category>A/B Testing</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Wed, 03 Jun 2026 14:54:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/google-fleet-ab-experimentation/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-06-03T14:54:00Z</dc:date>
      <dc:identifier>/news/2026/06/google-fleet-ab-experimentation/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Choosing Your AI Copilot: Maximizing Developer Productivity</title>
      <link>https://www.infoq.com/presentations/choosing-ai-copilot/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/presentations/choosing-ai-copilot/en/mediumimage/medium-1779867439150.jpg"/&gt;&lt;p&gt;Sepehr Khosravi discusses the evolution of developer productivity tools. Evaluating the strengths of tools like Cursor and Claude Code, he explains actionable techniques for senior engineers - including context engineering, custom rules, and Model Context Protocol (MCP) integrations. He shares real-world benchmarks and strategic frameworks for balancing AI adoption with clean code quality.&lt;/p&gt; &lt;i&gt;By Sepehr Khosravi&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>Artificial Intelligence</category>
      <category>QCon AI 2025</category>
      <category>Agents</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>presentation</category>
      <pubDate>Wed, 03 Jun 2026 11:05:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/choosing-ai-copilot/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Sepehr Khosravi</dc:creator>
      <dc:date>2026-06-03T11:05:00Z</dc:date>
      <dc:identifier>/presentations/choosing-ai-copilot/en</dc:identifier>
    </item>
    <item>
      <title>Article: Two Misconfigurations That Caused Spark OOM Failures on Kubernetes</title>
      <link>https://www.infoq.com/articles/spark-oom-kubernetes-misconfigurations/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/articles/spark-oom-kubernetes-misconfigurations/en/headerimage/spark-oom-kubernetes-misconfigurations-header-1780044756757.jpg"/&gt;&lt;p&gt;After migrating Spark pipelines to Azure Kubernetes Service, two infrastructure settings interacted destructively: spark.kubernetes.local.dirs.tmpfs=true backed shuffle spill with RAM instead of disk, and a hard podAffinity rule forced all executors onto one node. Together, they caused repeated OOM kills invisible to standard diagnostics.&lt;/p&gt; &lt;i&gt;By Pranav Bhasker&lt;/i&gt;</description>
      <category>Apache Spark</category>
      <category>Cloud</category>
      <category>Kubernetes</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 03 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/spark-oom-kubernetes-misconfigurations/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Pranav Bhasker</dc:creator>
      <dc:date>2026-06-03T09:00:00Z</dc:date>
      <dc:identifier>/articles/spark-oom-kubernetes-misconfigurations/en</dc:identifier>
    </item>
    <item>
      <title>Node.js Moves to One Major Release Per Year, Starting with Node 27</title>
      <link>https://www.infoq.com/news/2026/06/nodejs-release-changes/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/nodejs-release-changes/en/headerimage/generatedHeaderImage-1780400494858.jpg"/&gt;&lt;p&gt;Node.js will change its release schedule starting with version 27 in October 2026, moving from two major releases per year to one. All releases will become Long-Term Support (LTS), removing the distinction between odd and even versions. An Alpha channel for early testing will also be introduced. This decision addresses maintenance challenges and aims to align with user needs.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Versioning</category>
      <category>Semantic Versioning</category>
      <category>Release Management</category>
      <category>Web Development</category>
      <category>Node.js</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Wed, 03 Jun 2026 06:40:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/nodejs-release-changes/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-03T06:40:00Z</dc:date>
      <dc:identifier>/news/2026/06/nodejs-release-changes/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: The Human Toll of Incidents &amp; Ways To Mitigate It</title>
      <link>https://www.infoq.com/presentations/incident-response-mitigate/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/presentations/incident-response-mitigate/en/mediumimage/kyle-lexmond-medium-1779869148329.jpg"/&gt;&lt;p&gt;Kyle Lexmond explains how to handle the high-pressure environment of severe production outages. He discusses the critical distinction between mitigation and root-cause resolution, sharing personal experiences from harrowing incident rooms. He shares valuable operational strategies on overcoming cognitive overload, establishing blameless cultures, and optimizing systems for faster recovery.&lt;/p&gt; &lt;i&gt;By Kyle Lexmond&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>QCon San Francisco 2025</category>
      <category>Best Practices</category>
      <category>Incident Response</category>
      <category>DevOps</category>
      <category>presentation</category>
      <pubDate>Tue, 02 Jun 2026 12:50:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/incident-response-mitigate/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Kyle Lexmond</dc:creator>
      <dc:date>2026-06-02T12:50:00Z</dc:date>
      <dc:identifier>/presentations/incident-response-mitigate/en</dc:identifier>
    </item>
    <item>
      <title>OpenTelemetry Launches “Blueprints” Initiative to Simplify Enterprise Observability Adoption</title>
      <link>https://www.infoq.com/news/2026/06/opentelemetry-blueprints-launch/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/opentelemetry-blueprints-launch/en/headerimage/generatedHeaderImage-1779952030610.jpg"/&gt;&lt;p&gt;OpenTelemetry has introduced a new "Blueprints" initiative aimed at reducing the growing complexity of deploying and operating observability systems at scale.&lt;/p&gt; &lt;i&gt;By Craig Risi&lt;/i&gt;</description>
      <category>Observability</category>
      <category>OpenTelemetry</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Tue, 02 Jun 2026 12:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/opentelemetry-blueprints-launch/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Craig Risi</dc:creator>
      <dc:date>2026-06-02T12:00:00Z</dc:date>
      <dc:identifier>/news/2026/06/opentelemetry-blueprints-launch/en</dc:identifier>
    </item>
    <item>
      <title>Article: Why Vector Search Alone Isn't Enough: Hybrid Retrieval for RAG</title>
      <link>https://www.infoq.com/articles/vector-search-hybrid-retrieval-rag/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/articles/vector-search-hybrid-retrieval-rag/en/headerimage/vector-search-hybrid-retrieval-rag-header-1779972811121.jpg"/&gt;&lt;p&gt;In this article, author Aaditya Chauhan discusses the limitations of RAG pipelines based purely on vector search and how an internal omni-search application using Reciprocal Rank Fusion (RRF) that combines BM25 and vector results, can enhance the search solution.&lt;/p&gt; &lt;i&gt;By Aaditya Chauhan&lt;/i&gt;</description>
      <category>Generative AI</category>
      <category>Retrieval-Augmented Generation</category>
      <category>ElasticSearch</category>
      <category>vector databases</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Tue, 02 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/vector-search-hybrid-retrieval-rag/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Aaditya Chauhan</dc:creator>
      <dc:date>2026-06-02T09:00:00Z</dc:date>
      <dc:identifier>/articles/vector-search-hybrid-retrieval-rag/en</dc:identifier>
    </item>
    <item>
      <title>Google Workspace CLI: Unified Command-Line Tool Built for Humans and AI Agents</title>
      <link>https://www.infoq.com/news/2026/06/google-workspace-cli/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/google-workspace-cli/en/headerimage/generatedHeaderImage-1780314884182.jpg"/&gt;&lt;p&gt;Google has released a new CLI for Google Workspace, offering a unified interface for various services like Drive, Gmail, and Calendar. Built in Rust, the tool dynamically adjusts to API changes and features over 100 bundled skills. It requires Node.js and a Google Cloud project for setup. Initial community feedback is mixed, highlighting both its dynamic capabilities and setup challenges.&lt;/p&gt; &lt;i&gt;By Daniel Curtis&lt;/i&gt;</description>
      <category>Google</category>
      <category>CLI</category>
      <category>Web Development</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Tue, 02 Jun 2026 06:33:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/google-workspace-cli/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Daniel Curtis</dc:creator>
      <dc:date>2026-06-02T06:33:00Z</dc:date>
      <dc:identifier>/news/2026/06/google-workspace-cli/en</dc:identifier>
    </item>
    <item>
      <title>Java News Roundup: OpenJDK JEPs, Hazelcast, Quarkus, Hibernate, Koog, JHipster, Introducing Endive</title>
      <link>https://www.infoq.com/news/2026/06/java-news-roundup-may25-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/06/java-news-roundup-may25-2026/en/headerimage/java-news-roundup-image-1780348608154.jpg"/&gt;&lt;p&gt;This week's Java roundup for May 25th, 2026, features news highlighting: lifecycle changes with two of the JEPs that were targeted for JDK 27; the GA release of Koog 1.0; point releases of Hazelcast, Quarkus, Hibernate and JHipster; the eighth milestone release of Spring AI 2.0; and introducing Endive, a JVM-native WebAssembly (Wasm) runtime.&lt;/p&gt; &lt;i&gt;By Michael Redlich&lt;/i&gt;</description>
      <category>Endive</category>
      <category>Koog</category>
      <category>Open JDK</category>
      <category>Hibernate ORM</category>
      <category>JDK 27</category>
      <category>Hazelcast</category>
      <category>Spring AI</category>
      <category>Quarkus</category>
      <category>Java</category>
      <category>JHipster</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>news</category>
      <pubDate>Mon, 01 Jun 2026 21:30:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/06/java-news-roundup-may25-2026/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=global</guid>
      <dc:creator>Michael Redlich</dc:creator>
      <dc:date>2026-06-01T21:30:00Z</dc:date>
      <dc:identifier>/news/2026/06/java-news-roundup-may25-2026/en</dc:identifier>
    </item>
  </channel>
</rss>
