provider-boundary

name	provider-boundary
description	Keep auth, telemetry, flags, and external connectors behind provider interfaces
metadata	{"type":"Reference","origin":"harness-engineering/ch11","helpful":0,"harmful":0,"status":"active"}

Provider Boundary

Rules

1. Cross-cutting concerns go through provider interfaces.
2. Services use application vocabulary, not vendor SDK types.
3. Auth, telemetry, feature flags, and connectors are replaceable.
4. Connectors validate responses and define timeout/retry behavior.

Checklist

• No service imports Clerk, Auth0, Sentry, OpenTelemetry, or SaaS SDKs directly
• Provider interfaces use domain/application terms
• Unit tests can use fake providers
• Write connectors define idempotency and retry/no-retry behavior