| name | adobe-architecture-variants |
| description | Choose and implement Adobe architecture blueprints: standalone SDK integration,
Adobe App Builder serverless, and dedicated microservice with event-driven
Firefly/PDF pipelines. Decision matrix based on team size and throughput.
Trigger with phrases like "adobe architecture", "adobe blueprint",
"adobe app builder vs standalone", "adobe microservice".
|
| allowed-tools | Read, Grep |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","design","adobe"] |
| compatibility | Designed for Claude Code |
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
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': 'application/json',
},
body: JSON.stringify({ prompt: req.., : , : { : , : } }),
});
res.( result.());
} (: ) {
res.().({ : error. });
}
});