adobe-reliability-patterns

# Adobe Reliability Patterns ## Overview Production-grade reliability patterns for Adobe API integrations. Adobe APIs present unique challenges: IMS tokens expire after 24h, Firefly/Photoshop jobs are async with variable completion times, and rate limits vary by API. These patterns address each failure mode. ## Prerequisites - Understanding of circuit breaker pattern - `opossum` installed for circuit breaker (`npm install opossum`) - Queue infrastructure (BullMQ/Redis) for dead letter queue - Caching layer for fallback data ## Instructions ### Pattern 1: Circuit Breaker per Adobe API Different Adobe APIs fail independently — use separate circuit breakers: ```typescript import CircuitBreaker from 'opossum'; // IMS circuit breaker (auth failures cascade to everything) const imsBreaker = new CircuitBreaker( async () => { const res = await fetch('https://ims-na1.adobelogin.com/ims/token/v3', { method: 'POST', headers: { 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ client_id: process.env.ADOBE_CLIENT_ID!, client_secret: process.env.ADOBE_CLIENT_SECRET!, grant_type: 'client_credentials', scope: process.env.ADOBE_SCOPES!, }), }); if (!res.ok) throw new Error(`IMS ${res.status}`); return res.json(); }, { timeout: 10_000, // IMS should respond in 10s errorThresholdPercentage: 30, // Open after 30% errors resetTimeout: 60_000, // ...