<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sekka on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/ahmed-sekka/</link><description>Articles written by Sekka on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 10 Jun 2026 19:02:58 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/ahmed-sekka/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Spring Teams Don't Need a Second Runtime for AI Agents</title><link>https://foojayio.github.io/website/today/spring-ai-agents-no-second-runtime/</link><pubDate>Wed, 10 Jun 2026 19:02:58 +0000</pubDate><guid>https://foojayio.github.io/website/today/spring-ai-agents-no-second-runtime/</guid><description>&lt;p&gt;&lt;img src="https://foojayio.github.io/website/today/spring-ai-agents-no-second-runtime/hero-700x350.jpg" alt="" loading="lazy"&gt;
&lt;/p&gt;
&lt;br /&gt;
&lt;p&gt;&lt;em&gt;A JVM-native runtime for building, governing and operating AI agents on existing Spring infrastructure.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Every time a Spring team decides to add AI agents to a production system, the story tends to follow the same arc. A few prototypes are built, several frameworks are evaluated, and then a new reality emerges: the project is no longer just about adding agents. It is about operating a new platform.&lt;/p&gt;
&lt;p&gt;With that new runtime come new deployment pipelines, new monitoring mechanisms, additional security reviews, and new operational responsibilities.&lt;/p&gt;</description></item></channel></rss>