<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bezsonov Yuriy on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/bezsonov-yuriy/</link><description>Recent content in Bezsonov Yuriy on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 30 Apr 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/bezsonov-yuriy/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Production-Ready AI Agents with Java and Spring AI</title><link>https://javapro-en.svenruppert.com/building-production-ready-ai-agents-with-java-and-spring-ai/</link><pubDate>Thu, 30 Apr 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/building-production-ready-ai-agents-with-java-and-spring-ai/</guid><description>&lt;p&gt;Java developers have been building enterprise applications for decades, but when it comes to AI, the conversation has been dominated by Python. &lt;a href="https://spring.io/projects/spring-ai"&gt;Spring AI&lt;/a&gt; changes this situation. It brings the same patterns we know from Spring - dependency injection, auto-configuration, portable abstractions - to AI development.&lt;/p&gt;
&lt;p&gt;In January 2026 we built a sample agent application, and we want to share what we learned. The sample AI agent handles conversations with memory, answers questions from internal knowledge bases, uses external APIs, and integrates with existing microservices - all running on &lt;a href="https://aws.amazon.com/bedrock/"&gt;Amazon Bedro&lt;/a&gt;&lt;a href="https://aws.amazon.com/bedrock/"&gt;ck&lt;/a&gt;. If you want to try it yourself, the &lt;a href="https://catalog.workshops.aws/java-spring-ai-agents"&gt;Building AI Agents with Java and Spring AI&lt;/a&gt; workshop [1] walks you through typical challenges of Generative AI models and provides step by step solutions with code available on &lt;a href="https://github.com/aws-samples/java-on-aws"&gt;GitHub&lt;/a&gt; [2].&lt;/p&gt;</description></item><item><title>Java Performance Optimization with Agentic AI: Autonomous Diagnostics and Actionable Recommendations</title><link>https://javapro-en.svenruppert.com/java-performance-optimization-with-agentic-ai-autonomous-diagnostics-and-actionable-recommendations/</link><pubDate>Tue, 07 Apr 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-performance-optimization-with-agentic-ai-autonomous-diagnostics-and-actionable-recommendations/</guid><description>&lt;p&gt;&lt;a href="https://schedule.jcon.one/2026/session/1050952"&gt;&lt;figure class="post-figure"&gt;
 &lt;img src="https://javapro-en.svenruppert.com/uploads/2026/03/2026-Magazin-Artikel-Banner-1024x213.png" alt="" loading="lazy" decoding="async"&gt;
 
 
 
&lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Java performance diagnosis in production is manual, slow, and requires deep expertise. You get a Grafana alert, grab a thread dump, download a JFR recording, open it in JDK Mission Control, stare at flamegraphs, correlate with metrics — hours of work per incident. Most teams don&amp;rsquo;t have a dedicated performance engineer, so alerts get ignored or result in generic &amp;ldquo;add more replicas&amp;rdquo; responses.&lt;/p&gt;
&lt;p&gt;We built a system that does this autonomously. When a monitoring alert fires, it collects profiling data and thread dumps, extracts runtime metrics, generates flamegraphs, and sends everything to an AI model that produces a structured performance report — including root cause analysis and concrete code fixes with file paths and line numbers from the actual source repository. The pipeline runs on Kubernetes, triggered by Grafana webhooks, with results stored in Amazon S3.&lt;/p&gt;</description></item></channel></rss>