adobe-architecture-variants

# Adobe Architecture Variants ## Overview Three validated architecture blueprints for Adobe integrations: (A) direct SDK integration in existing app, (B) Adobe App Builder with Runtime actions, and (C) dedicated microservice with event-driven pipelines. ## Prerequisites - Understanding of team size and throughput requirements - Decision on which Adobe APIs to use (Firefly, PDF, Photoshop, Events) - Knowledge of deployment infrastructure - Growth projections for API usage ## Instructions ### Variant A: Direct SDK Integration (Simple) **Best for:** MVPs, small teams (1-5), < 100 API calls/day, single Adobe API ``` my-app/ ├── src/ │ ├── adobe/ │ │ ├── auth.ts # OAuth token management │ │ ├── firefly.ts # or pdf-services.ts — one API client │ │ └── types.ts │ ├── routes/ │ │ └── api/ │ │ └── generate.ts # Direct API call in route handler │ └── index.ts ├── .env # ADOBE_CLIENT_ID, ADOBE_CLIENT_SECRET └── package.json # @adobe/firefly-apis or @adobe/pdfservices-node-sdk ``` ```typescript // Direct integration — API call in route handler app.post('/api/generate', async (req, res) => { try { const token = await getCachedToken(); const result = await fetch('https://firefly-api.adobe.io/v3/images/generate', { method: 'POST', headers: { 'Authorization': `Bearer ${token}`, 'x-api-key': process.env.ADOBE_CLIENT_ID!, 'Content-Type': 'appl...