https://www.youngju.dev/blog 천천히 올바르게. AI Researcher & DevOps Engineer Youngju's blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology. ko fjvbn2003@gmail.com (Youngju Kim) fjvbn2003@gmail.com (Youngju Kim) Sat, 15 Aug 2026 00:00:00 GMT https://www.youngju.dev/blog/architecture/2026-08-15-guide-api-design.en https://www.youngju.dev/blog/architecture/2026-08-15-guide-api-design.en This guide reorganizes API design around a single axis: which decisions become irreversible the moment you publish, and which you can still change later. Resource boundaries, identifiers, method semantics, status codes, error formats, pagination, representing time and money, and versioning are ordered by cost of reversal, with claims grounded in RFC 9110, RFC 6585, and RFC 9457. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) api설계resthttprfc9110rfc9457버저닝페이지네이션 https://www.youngju.dev/blog/architecture/2026-08-15-guide-api-design.ja https://www.youngju.dev/blog/architecture/2026-08-15-guide-api-design.ja API 設計を一本の軸で並べ直します。公開した瞬間に戻せなくなる決定と、あとから変えられる決定を分け、リソース境界・識別子・メソッド意味論・ステータスコード・エラー形式・ページネーション・時刻と金額の表現・バージョニングを、戻すコストの順に整理します。根拠は RFC 9110、RFC 6585、RFC 9457 の原文です。 Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) api설계resthttprfc9110rfc9457버저닝페이지네이션 https://www.youngju.dev/blog/architecture/2026-08-15-guide-api-design https://www.youngju.dev/blog/architecture/2026-08-15-guide-api-design API 설계를 하나의 축으로 다시 배열합니다. 공개하는 순간 되돌릴 수 없게 되는 결정과 나중에 바꿀 수 있는 결정을 구분하고, 리소스 경계·식별자·메서드 의미론·상태 코드·오류 형식·페이지네이션·시간과 돈의 표현·버저닝을 되돌림 비용 순서로 정리합니다. RFC 9110, RFC 6585, RFC 9457 원문을 근거로 씁니다. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) api설계resthttprfc9110rfc9457버저닝페이지네이션 https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.en https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.en 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. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 에러처리재시도rfc9457타임아웃관측가능성resiliencesre https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.ja https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling.ja エラー処理を例外の文法ではなくインターフェース契約の一部として扱います。エラーを分類する二つの軸、例外と戻り値の論争の実際の軸、境界ごとにエラーを翻訳する規則、RFC 9457 に基づく HTTP エラー契約、冪等性なしの再試行の危険、タイムアウト予算、観測、そして利用者に何を伝えるかまでを整理します。 Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 에러처리재시도rfc9457타임아웃관측가능성resiliencesre https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling https://www.youngju.dev/blog/architecture/2026-08-15-guide-error-handling 에러 처리를 예외 문법이 아니라 인터페이스 계약의 일부로 다룹니다. 오류를 분류하는 두 축, 예외와 반환값 논쟁의 실제 축, 경계마다 오류를 번역하는 규칙, RFC 9457 기반 HTTP 오류 계약, 멱등성 없는 재시도의 위험, 타임아웃 예산, 관측, 그리고 사용자에게 무엇을 말할 것인지까지 정리합니다. Sat, 15 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) 에러처리재시도rfc9457타임아웃관측가능성resiliencesre