<?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/zh-cn/categories/incident-response/</link><description>Recent content in Incident Response on Neat Guy Coding</description><generator>Hugo -- gohugo.io</generator><language>zh-cn</language><copyright>© 2026 NeatGuyCoding</copyright><lastBuildDate>Wed, 01 Sep 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://neatguycoding.com/zh-cn/categories/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>网关雪崩危机：同步 Redis 调用如何几乎摧毁我们的系统</title><link>https://neatguycoding.com/zh-cn/posts/spring-cloud-gateway-avalanche/</link><pubDate>Wed, 01 Sep 2021 00:00:00 +0000</pubDate><guid>https://neatguycoding.com/zh-cn/posts/spring-cloud-gateway-avalanche/</guid><description>深入探讨生产事件，其中我们的 Spring Cloud Gateway 由于阻塞的 Redis 操作而经历了级联故障。了解响应式环境中的同步 API 调用如何导致线程饥饿，导致健康检查失败和系统范围的雪崩，以及使用异步模式的完整解决方案。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://neatguycoding.com/posts/spring-cloud-gateway-avalanche/featured.jpg"/></item></channel></rss>