<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microservices on Neat Guy Coding</title><link>https://neatguycoding.com/categories/microservices/</link><description>Recent content in Microservices on Neat Guy Coding</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 NeatGuyCoding</copyright><lastBuildDate>Wed, 02 Mar 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://neatguycoding.com/categories/microservices/index.xml" rel="self" type="application/rss+xml"/><item><title>The Hidden Performance Killer: Why Code Location in Logs Can Destroy Your Microservice Performance</title><link>https://neatguycoding.com/posts/log-with-position/</link><pubDate>Wed, 02 Mar 2022 00:00:00 +0000</pubDate><guid>https://neatguycoding.com/posts/log-with-position/</guid><description>Discover how enabling code location in logs can cause severe CPU performance issues in microservices, especially reactive applications. This deep-dive analysis reveals the hidden costs of stack walking in Log4j2 and provides actionable solutions for high-throughput systems.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://neatguycoding.com/posts/log-with-position/featured.jpg"/></item></channel></rss>