<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident Response on Neat Guy Coding</title><link>https://neatguycoding.com/categories/incident-response/</link><description>Recent content in Incident Response on Neat Guy Coding</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 NeatGuyCoding</copyright><lastBuildDate>Wed, 01 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://neatguycoding.com/categories/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>Gateway Avalanche Crisis: How Synchronous Redis Calls Nearly Brought Down Our System</title><link>https://neatguycoding.com/posts/spring-cloud-gateway-avalanche/</link><pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate><guid>https://neatguycoding.com/posts/spring-cloud-gateway-avalanche/</guid><description>A deep dive into a production incident where our Spring Cloud Gateway experienced cascading failures due to blocking Redis operations. Learn how synchronous API calls in reactive environments can cause thread starvation, leading to health check failures and system-wide avalanches, plus the complete solution using async patterns.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://neatguycoding.com/posts/spring-cloud-gateway-avalanche/featured.jpg"/></item></channel></rss>