Python Integrations and Resilience

Overview

External integrations stay reliable when provider-specific details hide behind explicit client boundaries, and every outbound operation carries a defined reliability policy that is tested against both success and failure paths.

Treat these recommendations as preferred defaults. When project constraints demand deviation, call out tradeoffs and compensating controls (tests, observability, rollback).

When to Use

• Designing or reviewing client boundaries around external APIs or provider SDKs.
• Adding or auditing timeout, retry, or idempotency policy on outbound calls.
• Writing contract or resilience tests for provider integrations.
• Diagnosing contract drift between a client wrapper and the upstream provider.
• Refactoring domain logic that has coupled itself to a specific provider SDK.

When NOT to Use