<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alexius Dionysius Diakogiannis on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/alexius-diakogiannis/</link><description>Articles written by Alexius Dionysius Diakogiannis on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 15 Jan 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/alexius-diakogiannis/index.xml" rel="self" type="application/rss+xml"/><item><title>The Ultimate 10 Years Java Garbage Collection Guide (2016–2026) - Choosing the Right GC for Every Workload</title><link>https://foojayio.github.io/website/today/the-ultimate-10-years-java-garbage-collection-guide-2016-2026-choosing-the-right-gc-for-every-workload/</link><pubDate>Thu, 15 Jan 2026 10:00:00 +0000</pubDate><guid>https://foojayio.github.io/website/today/the-ultimate-10-years-java-garbage-collection-guide-2016-2026-choosing-the-right-gc-for-every-workload/</guid><description>&lt;p&gt;Memory management remains the primary factor for application performance in enterprise Java environments. Between 2017 and 2025, the ecosystem shifted from manual tuning to architectural selection. Industry data suggests that 60 percent of Java performance issues and 45 percent of production incidents in distributed systems stem from suboptimal Garbage Collection (GC) behavior. This guide provides a strategic framework for selecting collectors based on workload characteristics. It covers the transition from legacy collectors to Generational ZGC, analyzing trade-offs regarding throughput, latency, and hardware constraints with mathematical precision.&lt;/p&gt;</description></item></channel></rss>