참고 자료 · 18

API 통합을 장애에 대한 복원력 있게 만드십시오.

종속성을 매핑하고, 재시도 횟수를 제한하고, 외부 장애 발생 시에도 필수 여정을 계속 사용할 수 있도록 유지하십시오.

업데이트됨 · 20 min

분리된 광케이블, 검은 네트워크 랙, 버건디 서류철과 황동 램프가 있는 가상의 무인 통신실 AI로 생성한 편집용 일러스트

이 가이드가 달성하는 목표

  • API를 비즈니스 여정에 연결
  • 바인딩된 호출 및 재시도
  • 성능 저하 시 운영 계획 수립
  • 복구 측정

빠른 확인

  • 어떤 여정이 각 공급자에 의존하는가?
  • 모든 호출에 타임아웃이 설정되어 있는가?
  • 재시도가 작업을 중복해서 수행할 수 있는가?
  • 오류 발생 시 사용자에게 어떤 화면이 표시되는가?
  • 정상 서비스 복귀 승인 권한자는 누구인가?

단계별 방법

  1. 1

    호출 매핑

    모든 통합을 교환된 데이터, 계약, 담당자 및 여정 단계에 연결합니다. 사용자를 차단하는 동기 호출을 식별합니다.

    결과물: 우선순위가 지정된 종속성 맵

  2. 2

    시간 예산 설정

    각 호출에 대한 타임아웃과 여정별 총 예산을 정의합니다. 서비스 체인이 대기 시간을 증가시키지 않도록 합니다.

    결과물: 타임아웃 및 임계값 매트릭스

  3. 3

    제한된 재시도 횟수

    반복해도 안전한 작업만 재시도합니다. 멱등성을 테스트하고, 재시도 횟수를 제한하고, 적절한 백오프를 적용하여 재시도 횟수를 분산합니다.

    결과물: 테스트 완료된 재시도 정책

  4. 4

    성능 저하 시 운영 계획 수립

    장애 발생 시 사용 가능한 데이터, 대기열에 저장할 데이터, 명확한 메시지 등을 결정합니다.

    결과물: 여정별 대체 동작

  5. 5

    장애 시뮬레이션

    제어된 환경에서 지연 시간, 잘못된 응답 및 장애를 발생시킵니다. 부하, 데이터, 인터페이스 및 복구를 확인합니다.

    결과물: 장애 테스트 결과

  6. 6

    결과 모니터링

    오류, 지연 시간, 대기열 및 실제로 손실된 비즈니스 작업을 추적합니다. 에스컬레이션 및 공급업체 조정 담당자를 지정합니다.

    결과물: 대시보드 및 복구 절차

관리 지표

지표측정 대상첫 번째 조치
매핑된 여정알려진 종속성이 있는 필수 여정알 수 없는 호출에 담당자 할당
시간 예산여정 마감 시간 내 호출연쇄 대기 검토
안전한 재시도부작용 없는 반복 작업멱등성 추가 또는 재시도 제거
성능 저하 테스트관찰된 사용자 결과가 포함된 장애 시나리오연속성 및 커뮤니케이션 개선

일반적인 실수

  • 과부하 서비스에 대한 무제한 재시도
  • 멱등성이 없는 쓰기 반복
  • 레이블이 지정되지 않은 오래된 데이터 뒤에 장애 숨기기
  • 공급자 응답률만 측정

자주 묻는 질문

모든 요청을 재시도해야 할까요?

아니요. 재시도는 특정 일시적 오류를 해결하는 데 도움이 되지만 전체 마감 시간, 멱등성 및 공급자 부하를 준수해야 합니다.

회로 차단기로 충분합니까?

일부 통화는 보호하지만 사용자 경험이나 대기 중인 작업의 복구를 정의하지는 않습니다.

무엇을 먼저 측정해야 할까요?

필수 여정에 미치는 영향: 소요 시간, 손실 또는 지연된 작업 및 복구 품질

참고 자료: 데이터, 용도와 한계

문서 검토일 .

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

참고 자료: 데이터, 용도와 한계
출처와 목적확인된 데이터 또는 기준사용 방법유지해야 할 한계
OASIS · TAXII 2.1

Exchange threat intelligence through an application protocol.

TAXII 2.1 is an OASIS Standard dated 10 June 2021. It includes service discovery and access to collections. Test authentication, collection permissions, pagination and recovery after interruption. Record which objects were actually received and processed.

방법 자세히 보기 →

TAXII transports data; it replaces neither the content model nor assessment of reliability.

ETag, HTTP 캐시 및 동시 변경

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

A retry must not overwrite a newer version

Separate a network failure, a failed precondition and the retry decision. A 412 is not an invitation to resend the same write repeatedly.

  • Keep the ETag with the representation used to prepare PUT.
  • After 412, read again and resolve the conflict; backoff alone does not reconcile edits.
  • Document duplicates and requests with unknown outcomes separately: they are outside this precondition simulator.

Explore ETag comparisons and the simulator →

References reviewed · RFC 9110 · §13 · RFC 9111 · RFC 6585 · §3

멱등성과 API 재시도 계약

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Compare an HTTP property with a provider contract

HTTP idempotence concerns the intended effect of identical requests. Application retry keys belong to the API’s contract. Stripe details below are attributed to its documentation accessed on 22 October 2026, apply to its APIs and are not simulated by the budget model.

Lost response: three checks before another write
Lost response: three checks before another write After a lost response, connect the operation to verified business state. Then check operation identity, retry contract and context. Finally choose reconciliation or a bounded retry; arbitrarily changing the key does not prove absence of an earlier effect. Unknown result Reconcile business state Contract and identity Same operation checked context Bounded decision Retry or verification

After a lost response, connect the operation to verified business state. Then check operation identity, retry contract and context. Finally choose reconciliation or a bounded retry; arbitrarily changing the key does not prove absence of an earlier effect.

Six Stripe differences or limits to document

Six Stripe differences or limits to document
ComparisonAPI v1API v2
Methods accepting keysPOST accepts keys. Sending one on GET or DELETE has no effect under this contract.POST and DELETE accept keys; GET is idempotent by definition and a key has no effect.
Reused resultAfter execution begins, the initial status and body are saved; a retry can return the same 500 error.Successful work is not repeated. Failed or partially failed work can be retried for an updated response; an impossible replay returns an explanatory error.
Window and retentionThe dedicated page permits pruning after at least 24 hours. A key reused after pruning creates a new request.Documented replay is within 30 days for the same API and account or sandbox.
Parameters and scopeThe layer compares parameters with the original request and rejects incompatible reuse.Same API and same account or sandbox are part of replay conditions; review the exact endpoint contract.
Before executionA validation failure or concurrency conflict that does not initiate the endpoint saves no idempotent result, according to the v1 page.Do not copy a v1 exception without checking v2 documentation and the endpoint being used.
Durable identityA key should remain tied to one intention and its parameters; documentation advises against sensitive data in keys.Automatic service-side key generation does not remove the client’s need to associate retries with the correct operation.

Status is not everything: Stripe-Should-Retry

Status is not everything: Stripe-Should-Retry
Documented valueStripe guidanceLimit
trueRetry using exponential backoff under the error-handling documentation.Also check operation identity, context, budget and contract.
falseDo not retry the request.Do not replace this signal with a generic “every 5xx can be replayed” test.
AbsentDecide using status and other response information.Absence neither guarantees no effect nor requires a retry.

Four retry situations needing different evidence

Response lost after sending

A client does not receive a creation response.

Find the operation and state in the authorised source; retain the key if the contract permits replay of that same intention.

A new key can describe a new operation and produce another effect.

Same key, changed parameters

The client changes content while reusing a key.

Compare parameters with the contract and separate correcting a request from repeating it identically.

The described v1 contract rejects incompatible parameters; do not work around this with a new key without a business decision.

Key outside its replay window

The application wants to replay an old request.

Review duration, API, account and business state; do not assume the provider retains the first result forever.

An old key is not evidence of permanent uniqueness.

Two workers for one effect

Two workers both read “effect absent”.

Test atomic claiming of the local effect and the external-effect contract; retain both receipts.

A preliminary SELECT or local constraint alone cannot guarantee uniqueness at a remote provider.

Keep three identities separate

Keep three identities separate
IdentityRole in a webhook exampleLimit
Request keyRecognise a repeated client request under an API contract.It is not automatically the identifier of a received event.
Event identifierConnect repeat deliveries from a provider and its context.Different events can concern the same business effect.
Business-effect keyPrevent a repeated chosen local business action using an appropriate atomic mechanism.A remote effect needs its own guarantee, controlled recovery and reconciliation.

Explore Retry-After and the retry model →

Primary sources and limits

The RFCs define the cited HTTP elements. AWS describes design choices and Stripe documents its own APIs. Budgets, local waits, cases and diagrams are educational: they neither measure your service nor execute requests.

References reviewed

OAuth/OIDC: 대상과 권한

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Token renewal does not replace access-removal procedures

Separate session, access-token and refresh-token lifecycles in operations. Local sign-out does not prove they all become invalid simultaneously.

  • Measure residual access using authorised test accounts and objects.
  • Exercise expiry, revocation and provider outage without logging secrets.
  • Record expected responses and the owner responsible for restoring the integration.

See token recipients and the ten OAuth/OIDC cases →

Sources reviewed on · IETF · RFC 9700 · OAuth 2.0 Security BCP · IETF · RFC 9068 · JWT access token profile · OpenID Foundation · OpenID Connect Core 1.0 · IETF · RFC 8725 · JWT Best Current Practices · IETF · RFC 6749 · OAuth 2.0 framework

웹훅: 서명과 재전송

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

API recovery and webhook recovery follow different contracts

For incoming notifications, track the event, transport attempt and business effect separately. A signature authenticates a message; it is not an idempotency key.

  • Retain required raw bytes and authenticate each new attempt.
  • Plan provider-specific recovery: Stripe can retry automatically; GitHub does not automatically redeliver failures.
  • Test lost responses, concurrency and post-outage reconciliation.

See webhook signatures, digests and the ten cases →

Sources reviewed on · Stripe · Webhooks · Stripe · Manage webhook endpoints · GitHub · Validating webhook deliveries · GitHub · Best practices for using webhooks · GitHub · Handling failed webhook deliveries

SSRF: URL과 연결

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

A retry does not change destination policy

Resilience for a URL importer must preserve egress controls. A fallback address, proxy or redirect introduces another step to verify, even when the original string passed the application contract.

  • Use the same parser and fields for validation and the HTTP client.
  • Bind validated addresses to actual connections while preserving TLS and the original hostname.
  • Test refusals and limits in an authorized lab without probing third-party services.

Read the 12 cases and connection controls →

Sources reviewed on · OWASP · SSRF Prevention Cheat Sheet · WHATWG · URL Living Standard · AWS EC2 · Instance metadata options · IETF · RFC 3849

페이지 나누기: 일관성과 재개

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Recovery follows the batch actually retained

A retry needs to know which objects were retained and under which view. Advancing continuation before confirming a batch can lose data; rereading requires deduplication and an external-effects policy.

  • Test a crash between batch retention and checkpointing.
  • Do not infer completion from page size alone.
  • Recheck permissions and reference validity on every recovery.

Compare computed reads and recoveries →

Sources reviewed on · Google · AIP-158 Pagination · PostgreSQL 18 · LIMIT and OFFSET · PostgreSQL 18 · Row constructor comparison · PostgreSQL 18 · Transaction isolation · OWASP · API1:2023 Broken Object Level Authorization

API 오류: 유형, 상태 및 증거

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Handle an error without parsing its sentence

An API client may receive a translated title, missing member or unfamiliar extension. Preserve decisions based on the documented type and HTTP status, then connect a safe action to the context.

  • Compare received status and JSON status without silently replacing either.
  • Test absent type, string status instead of a number, and an unknown extension.
  • Separate person-facing text, business code and occurrence reference.

Explore problem types and eight fictional responses →

IETF · M. Nottingham, E. Wilde, S. Dalal · RFC 9457 · July 2023 · obsoletes RFC 7807 · §3.1, §3.2, §4.2, §5

API 사용 중단과 종료

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

An integration can remain available after being deprecated. Planning migration therefore requires separating the announced lifecycle, actual service state and dependencies still to move. This dossier adds relevant HTTP signals, deadline interpretation and exit checks for API, operations and security teams.

References: RFC 9745 (March 2025) for Deprecation and RFC 8594 (May 2019, Informational) for Sunset. When both dates are provided, Sunset must not precede Deprecation. Equal dates satisfy that ordering; they do not establish that sufficient notice was provided.

IETF · RFC 9745 · Deprecation · Standards Track · March 2025 · §2–5 · consulted 2026-10-23

IETF · RFC 8594 · Sunset · Informational · May 2019 · §3–5, §8 · consulted 2026-10-23

Four signals for planning migration

Four signals for planning migration
SignalWhat it communicatesFormat or natureLimitation to retain
DeprecationAnnounces past or future deprecation of the contextual resource.Structured Fields Date, not a textual HTTP-date.Does not by itself change resource behaviour.
SunsetIndicates when the resource is likely to stop responding.HTTP-date; emitted IMF-fixdate uses GMT.A retirement hint, not an availability guarantee before or after.
Link · rel="deprecation"Points to deprecation documentation.A link relation, not a date.Documentation may be exposed before a dated announcement.
Link · rel="sunset"Points to retirement information or policy.A link relation, not a deadline.Read the scope and conditions actually documented.

Two date formats that must not be interchanged

Two date formats that must not be interchanged
Educational exampleReadingReference
Deprecation: @168816959930 June 2023 at 23:59:59 UTC. The number represents seconds since the Unix epoch, prefixed with @.RFC 9745 §2.1; RFC 9651 §3.3.7
Sunset: Sun, 30 Jun 2024 23:59:59 GMTCIE example in IMF-fixdate: English weekday, date and GMT. Do not substitute an ISO timestamp here.RFC 8594 §3; RFC 9110 §5.6.7

IETF · RFC 9651 · Structured Fields · Standards Track · September 2024 · §3.3.7 · consulted 2026-10-23

IETF · RFC 9110 · HTTP semantics · Internet Standard · June 2022 · §5.6.7 · consulted 2026-10-23

UTC 일정 읽기

Compare timestamps already normalised to UTC. The reader does not decode HTTP headers: it works on dates you have extracted and checked. Both deadlines are optional; the reading timestamp is required. Examples use a fixed reference time so results remain reproducible.

CIE input profile: YYYY-MM-DDTHH:mm:ssZ, years 1970 to 2099, seconds 00 to 59, without fractions, spaces or numeric offsets. These limits keep the workshop predictable; they do not describe the full RFC syntax. A blank date means “not supplied in this exercise”, not “this policy does not exist”.

Local calculation without network requests, import, storage or export. The reader establishes neither availability, compatibility nor complete header conformance. It derives no minimum migration notice: check the contract, policy, dependencies and provider contact. Reaching a Sunset date remains an announced hint, not proof of actual shutdown.

Deadline offsets from the reading time are signed: negative means past, zero means reached, positive means future. Sunset − Deprecation compares the announcements; a negative interval signals inconsistent ordering. Values are exact seconds within the profile, not local calendar days.

Nine reading scenarios, available without JavaScript

V01 · Future deprecation
Future deprecation
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-11-01T00:00:00Z2026-12-01T00:00:00Z2026-10-23T00:00:00ZTwo future deadlines separated by 2,592,000 seconds. This timeline does not establish contractually sufficient notice.
V02 · Deprecation already effective
Deprecation already effective
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-10-01T00:00:00Z2026-12-01T00:00:00Z2026-10-23T00:00:00ZDeprecation is past and Sunset is future. This does not mean the resource has already stopped working.
V03 · Sunset date reached
Sunset date reached
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-10-01T00:00:00Z2026-10-23T00:00:00Z2026-10-23T00:00:00ZSunset minus reading time is zero. Check actual service state and migration; the field remains a hint.
V04 · Conflicting order
Conflicting order
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-11-01T00:00:00Z2026-10-01T00:00:00Z2026-10-23T00:00:00ZSunset precedes Deprecation by 2,678,400 seconds. Seek clarification rather than assuming a coherent schedule.
V05 · Sunset only
Sunset only
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
—2026-12-01T00:00:00Z2026-10-23T00:00:00ZA retirement date is supplied, but no Deprecation date is provided in the exercise. Do not invent the missing date.
V06 · Deprecation only
Deprecation only
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-10-01T00:00:00Z—2026-10-23T00:00:00ZDeprecation is effective at the chosen time; no retirement date is supplied. Do not infer a support period.
V07 · No deadlines supplied
No deadlines supplied
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
——2026-10-23T00:00:00ZThe absence of dates in this input guarantees neither longevity nor the absence of an external policy.
V08 · Impossible calendar date
Impossible calendar date
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-02-29T00:00:00Z2026-12-01T00:00:00Z2026-10-23T00:00:00Z2026 is not a leap year. Input is rejected instead of silently normalising into March.
V09 · Both dates equal the reading time
Both dates equal the reading time
Normalised DeprecationNormalised SunsetUTC reading timestampExpected reading
2026-10-23T00:00:00Z2026-10-23T00:00:00Z2026-10-23T00:00:00ZOrdering satisfies the non-earlier relation with a zero interval. This does not establish that a migration period was offered.

Collect evidence for a controlled exit

Collect evidence for a controlled exit
Suggested checkVerifiable record
ScopeAffected resource, operations, version, environment and policy; do not generalise one response to every route.
ConsumersOwners, SDKs, scheduled jobs and partner integrations; reconcile declared inventory and observed use.
TimelineAnnouncement origin, UTC dates, updates and authorised provider contact.
ReplacementTest existing journeys on the target: data, permissions, errors, pagination and side effects.
CoexistenceCutover criterion, rollback strategy and treatment of in-flight or replayed operations.
ClosureCheck remaining consumers, remove obsolete secrets, update documentation and verify the business outcome.

A useful alert connects a deadline to a consumer and a verifiable action. Record what was announced, what was actually tested and what remains unknown. If dates conflict, ask the provider for clarification before turning the timeline into a cutover schedule.

Sources, editions and credits

Original CIE summaries informed by RFCs 9745, 8594, 9651 and 9110. Fictional educational scenarios and checks. The comparison program is original; no RFC algorithm is reproduced. The second date example is written by CIE using GMT, following HTTP’s emission format.

IETF · RFC 9745 · Deprecation · Standards Track · March 2025 · §2–5 · consulted 2026-10-23

SHA-256 : 84d1c7e47062f92b08f12e83eee258c59cf6adef970fae938d92c30fa0a0411f

IETF · RFC 8594 · Sunset · Informational · May 2019 · §3–5, §8 · consulted 2026-10-23

SHA-256 : 1a20d634f9cb1d68295b5c501d32c68f43799dfbdb1e8b4ac21707b8c273aa80

IETF · RFC 9651 · Structured Fields · Standards Track · September 2024 · §3.3.7 · consulted 2026-10-23

SHA-256 : fe27f2ec8819911afbe4bd11f6fcb947580da4c49e5423a1fff960e252ced26d

IETF · RFC 9110 · HTTP semantics · Internet Standard · June 2022 · §5.6.7 · consulted 2026-10-23

SHA-256 : 21c1cdce6ab0e5509b04d84a28000836c7a087cf786efe6f04877ebfff47232a

공식 참조

참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.

참고 자료 확인일 .