<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Fail-Fast on wid's blog</title><link>https://wid-blog.github.io/tags/fail-fast/</link><description>Recent content in Fail-Fast on wid's blog</description><generator>Hugo</generator><language>ko</language><lastBuildDate>Sat, 15 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/tags/fail-fast/index.xml" rel="self" type="application/rss+xml"/><item><title>Circuit Breaker</title><link>https://wid-blog.github.io/posts/tech/design-pattern/circuit-breaker/</link><pubDate>Sat, 15 Feb 2025 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/posts/tech/design-pattern/circuit-breaker/</guid><description>Circuit Breaker 의 차단 트리거와 회복 전략은 함께 설계되어야 한다. 회복 없는 차단은 의존성을 영구히 끊고, 차단 기준 없는 회복은 무의미한 cycling 이다.</description></item></channel></rss>