create-a-backend
Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- create-a-backend
- summary
- Match backend workloads to the right architecture
- metadata
- { "docs": [ "https://vercel.com/docs/frameworks/backend", "https://vercel.com/docs/functions", "https://vercel.com/docs/services", "https://vercel.com/docs/queues", "https://vercel.com/docs/workflow", "https://vercel.com/docs/storage" ], "sitemap": "https://vercel.com/sitemap.xml", "priority": 7, "pathPatterns": [ "Dockerfile.vercel", "Containerfile.vercel" ], "promptSignals": { "allOf": [ [ "backend", "vercel" ], [ "backend", "docker" ], [ "backend", "node" ], [ "backend", "python" ], [ "backend", "queue" ] ], "anyOf": [ "api", "database", "service", "workflow" ], "noneOf": [], "phrases": [ "backend on vercel", "vercel backend", "build a backend", "create a backend", "deploy my backend", "backend architecture" ], "minScore": 6 } }
- retrieval
- { "aliases": [ "Vercel backend", "backend architecture", "backend framework" ], "intents": [ "build a backend", "choose backend products", "deploy an existing API or server", "select a Node.js or Python backend framework" ], "entities": [ "Vercel Functions", "Vercel Services", "Vercel Queues", "Vercel Workflow", "Vercel Marketplace", "container images" ] }
- description
- Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.
02 资源文件 1
- 参考文档agents/openai.yaml190 B
03 SKILL.md 正文
Create a Backend
Help the user create a backend by choosing an architecture before reaching for implementation details. Start from the workload, not the programming language. Vercel runs complex backend applications, not just frontends.
Product map
| Need | Vercel product |
|---|---|
| HTTP APIs, webhooks, streaming, or framework server code | Vercel Functions with Fluid compute |
| Bidirectional realtime connections (WebSockets) | Vercel Functions with Fluid compute; no separate realtime service required |
| A frontend and one or more backends (API endpoints) that deploy together | Vercel Services |
| An existing Dockerfile, custom runtime, or system dependencies | Container images on Vercel Functions, optionally composed with Services |
| Durable multi-step work with retries, sleeps, or external events | Vercel Workflow |
| Background jobs, buffering, fan-out, or direct message routing | Vercel Queues |
| Scheduled HTTP work | Vercel Cron Jobs; use Workflow when the job itself must be durable |
| Postgres, Redis, NoSQL, vector, or other application data | Storage integrations from the Vercel Marketplace |
| Files and user uploads | Vercel Blob |
| Global, read-heavy configuration | Global Config |
Use Functions for the normal request/response backend. Use Services when independently built components should share one deployment, routing layer, preview URL, and rollback. Use separate Vercel projects when components need independent release cycles.
Prefer a native Functions runtime for supported frameworks. Use container images when the application already has a Dockerfile or requires a custom runtime or system dependencies. They run as autoscaling, stateless Functions rather than always-on container hosts.
Choose Queues for background jobs, buffering, fan-out, and message routing. Choose Workflow for durable multi-step business logic.
Databases and data stores
Provision data stores through the Marketplace so credentials are injected into the project and environments stay connected. Check the current catalog before choosing a provider.
- Postgres: Neon, Supabase, AWS/Aurora, Nile, Prisma
- MySQL: AWS/Aurora
- Redis and key-value: Upstash, Redis
- Document and NoSQL: MongoDB Atlas, AWS
- SQLite: Turso
- Realtime application backend: Convex
- Analytics: MotherDuck
Keep the database close to the Functions region and use a serverless-compatible connection or pool.
Backend frameworks
Vercel provides first-class backend examples and integrations for these frameworks:
- Node.js and TypeScript: Elysia, Express, Fastify, H3, Hono, Koa, NestJS, Nitro, and xmcp. Next.js Route Handlers are the natural choice when the backend belongs to a Next.js application.
- Python: FastAPI, Flask, and Django. Other WSGI or ASGI applications can run when they export a compatible
app, with additional configuration as needed. - Go: supported as a Vercel Functions runtime.
Frontend and backend combinations, for example a Next.js/Vite/SvelteKit frontend with a FastAPI/Flask/Express/Go backend, can be deployed together in one project using Services.
Prefer the user's existing framework. For a new project, choose based on ecosystem and application needs.
Work sequence
- Identify synchronous requests, asynchronous work, persistent data, and independently deployed components.
- Select the products from the map, then select the framework.
- Load the focused skill for implementation:
vercel-functions,vercel-services,workflow,vercel-storage, ormarketplace. - Confirm function limits, regions, environment variables, observability, and current product availability in the official docs before deployment.
04 同仓库更多 Skills
business-data
暂无简介
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
workflow
Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.