Skip to content

[skills] Sync create-a-backend with current docs #214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
molebox merged 1 commit into from
Sep 25, 2026
Merged

[skills] Sync create-a-backend with current docs #214

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions skills/create-a-backend/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ metadata:
- "https://vercel.com/docs/functions"
- "https://vercel.com/docs/services"
- "https://vercel.com/docs/queues"
- "https://vercel.com/docs/workflow"
- "https://vercel.com/docs/workflows"
- "https://vercel.com/docs/storage"
sitemap: "https://vercel.com/sitemap.xml"
pathPatterns:
Expand Down Expand Up @@ -67,11 +67,11 @@ Help the user create a backend by choosing an architecture before reaching for i
| Bidirectional realtime connections (WebSockets) | **[Vercel Functions with Fluid compute](https://vercel.com/docs/functions/websockets)**; no separate realtime service required |
| A frontend and one or more backends (API endpoints) that deploy together | **[Vercel Services](https://vercel.com/docs/services)** |
| An existing Dockerfile, custom runtime, or system dependencies | **[Container images](https://vercel.com/docs/functions/container-images)** on Vercel Functions, optionally composed with Services |
| Durable multi-step work with retries, sleeps, or external events | **[Vercel Workflow](https://vercel.com/docs/workflow)** |
| Durable multi-step work with retries, sleeps, or external events | **[Vercel Workflows](https://vercel.com/docs/workflows)** |
| Background jobs, buffering, fan-out, or direct message routing | **[Vercel Queues](https://vercel.com/docs/queues)** |
| Scheduled HTTP work | **[Vercel Cron Jobs](https://vercel.com/docs/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](https://vercel.com/marketplace/category/storage)** |
| Files and user uploads | **[Vercel Blob](https://vercel.com/docs/storage/vercel-blob)** |
| Files and user uploads | **[Vercel Blob](https://vercel.com/docs/vercel-blob)** |
| Global, read-heavy configuration | **[Global Config](https://vercel.com/docs/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.
Expand Down
Loading