
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sat, 15 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/재시도/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.en</guid>
    <title>The Complete Guide to Error Handling: Designing Failure as Part of the Contract</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.en</link>
    <description>This guide treats error handling as part of the interface contract rather than as exception syntax. It covers the two axes for classifying errors, the real axes of the exceptions-vs-return-values dispute, the rules for translating errors at each boundary, the HTTP error contract built on RFC 9457, why retries without idempotency are unsafe, timeout budgets, observability, and what to tell the user.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>에러처리</category><category>재시도</category><category>rfc9457</category><category>타임아웃</category><category>관측가능성</category><category>resilience</category><category>sre</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.ja</guid>
    <title>エラー処理完全ガイド: 失敗を契約として設計する</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.ja</link>
    <description>エラー処理を例外の文法ではなくインターフェース契約の一部として扱います。エラーを分類する二つの軸、例外と戻り値の論争の実際の軸、境界ごとにエラーを翻訳する規則、RFC 9457 に基づく HTTP エラー契約、冪等性なしの再試行の危険、タイムアウト予算、観測、そして利用者に何を伝えるかまでを整理します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>에러처리</category><category>재시도</category><category>rfc9457</category><category>타임아웃</category><category>관측가능성</category><category>resilience</category><category>sre</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling</guid>
    <title>에러 처리 완전 가이드: 실패를 계약으로 설계하기</title>
    <link>https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling</link>
    <description>에러 처리를 예외 문법이 아니라 인터페이스 계약의 일부로 다룹니다. 오류를 분류하는 두 축, 예외와 반환값 논쟁의 실제 축, 경계마다 오류를 번역하는 규칙, RFC 9457 기반 HTTP 오류 계약, 멱등성 없는 재시도의 위험, 타임아웃 예산, 관측, 그리고 사용자에게 무엇을 말할 것인지까지 정리합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>에러처리</category><category>재시도</category><category>rfc9457</category><category>타임아웃</category><category>관측가능성</category><category>resilience</category><category>sre</category>
  </item>

    </channel>
  </rss>
