Wrap providers behind stable internal adapters so provider-specific response formats do not leak through domain code.

How to apply it

Use timeouts, bounded retries, rate limits, and degradation behavior. Separate transient errors from permanent ones, request minimum scopes, and track integration health by provider and tenant.

Worked example

An email adapter exposes sendInvitation while handling provider API versions, rate limits, and safe error normalization.

Common mistakes to avoid

Retrying every error or calling external APIs directly from many controllers.

Practice task

Implement this concept in the capstone. Add one positive test, one negative or failure-path test, and a short note explaining the trade-off you chose.