<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sascha Möllering on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/sascha-m%C3%B6llering/</link><description>Recent content in Sascha Möllering on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 11 Jun 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/sascha-m%C3%B6llering/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating JVM Thread Dump Analysis with AI: Practical Observability for Java on Amazon ECS and EKS</title><link>https://javapro-en.svenruppert.com/automating-jvm-thread-dump-analysis-with-ai-practical-observability-for-java-on-amazon-ecs-and-eks/</link><pubDate>Thu, 11 Jun 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/automating-jvm-thread-dump-analysis-with-ai-practical-observability-for-java-on-amazon-ecs-and-eks/</guid><description>&lt;p&gt;Imagine the following scenario: a Java service that ran flawlessly yesterday suddenly starts consuming 90% CPU, barely responding to user requests. Users encounter timeouts, and the operations team is under immediate pressure to triage the incident. In these situations — whether the application appears stuck or CPU saturation has occurred — one of the most powerful diagnostic assets available is the thread dump. A thread dump captures the state of all JVM threads at a specific point in time, showing execution states, stack traces, and lock contention — the raw material needed to understand what the runtime is &lt;em&gt;actually doing&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Modernize Java Applications with Amazon EKS: A Cloud-Native Approach</title><link>https://javapro-en.svenruppert.com/modernize-java-applications-with-amazon-eks-a-cloud-native-approach/</link><pubDate>Tue, 19 Aug 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/modernize-java-applications-with-amazon-eks-a-cloud-native-approach/</guid><description>&lt;p&gt;Cloud-native development has become the cornerstone of modern application development, with containerization leading the charge in deployment strategies. For Java developers and enterprises with significant Java investments, the journey to cloud-native architecture presents both opportunities and challenges. This article explores how Amazon EKS, combined with cutting-edge technologies like &lt;a href="https://wiki.openjdk.org/display/crac"&gt;Coordinated Restore at Checkpoint (CRaC)&lt;/a&gt; and &lt;a href="https://quarkus.io/"&gt;Quarkus&lt;/a&gt;, is revolutionizing Java application deployment in the cloud.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://aws.amazon.com/eks/"&gt;Amazon Elastic Kubernetes Service (Amazon EKS)&lt;/a&gt; is a fully managed Kubernetes service that enables customers to run Kubernetes seamlessly in both AWS Cloud and on-premises data centers. In the cloud, Amazon EKS automates Kubernetes cluster infrastructure management. This is essential for scheduling containers, managing application availability, dynamically scaling resources, optimizing compute, storing cluster data, and performing other critical functions. With Amazon EKS, customers can leverage the robust performance, scalability, reliability, and availability of AWS infrastructure, as well as natively integrate with AWS networking, security, and storage services. To simplify running Kubernetes in on-premises environments, customers can use the same Amazon EKS clusters, features, and tools to run nodes on &lt;a href="https://aws.amazon.com/outposts/"&gt;AWS Outposts&lt;/a&gt; or their own infrastructure, or customers can use &lt;a href="https://aws.amazon.com/eks/eks-anywhere"&gt;Amazon EKS Anywhere&lt;/a&gt; for self-contained, air-gapped environments.&lt;/p&gt;</description></item></channel></rss>