create-a-backend

Plans backend architectures by mapping workloads to Vercel Functions, Services, Queues, and Workflow.

Updated Dec 17, 2022
One-click install
npx skills add https://github.com/Foodshareclub/foodshare-web --skill create-a-backend-foodshareclub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-a-backend
Source: https://github.com/Foodshareclub/foodshare-web/tree/main/.agents/skills/create-a-backend
Command: npx skills add https://github.com/Foodshareclub/foodshare-web --skill create-a-backend-foodshareclub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right backend architecture on Vercel is confusing when you must decide between Functions, Services, containers, Queues, Workflow, and Marketplace databases. This Skill guides that decision from the workload outward, before any implementation begins. ## Core Features & Use Cases - Workload-to-Product Mapping: Matches needs like HTTP APIs, WebSockets, background jobs, durable multi-step logic, and scheduled work to the correct Vercel product. - Framework Selection: Covers supported backend frameworks including Express, Fastify, Hono, NestJS, FastAPI, Flask, Django, and Go, plus container images for custom runtimes. - Database Guidance: Directs provisioning of Postgres, Redis, MongoDB, and other data stores through Vercel Marketplace integrations. - Use Case: You have an existing Express API with a Dockerfile and need background job processing. The Skill recommends container images on Vercel Functions combined with Vercel Queues, then points you to the focused implementation skills. ## Quick Start Use the create-a-backend skill to plan the architecture for deploying my FastAPI backend with a Postgres database on Vercel.

Frequently Asked Questions about create-a-backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a backend on Vercel?

Deploy a backend on Vercel using Vercel Functions with Fluid compute for HTTP APIs and webhooks. For existing Dockerfiles or custom runtimes, use container images on Functions, and compose multiple components with Vercel Services when they should deploy together.

What backend frameworks does Vercel support?

Vercel supports Node.js frameworks including Express, Fastify, Hono, NestJS, Koa, and Elysia, plus Python frameworks FastAPI, Flask, and Django. Go is also supported as a Functions runtime, and Next.js Route Handlers work for backends within Next.js apps.

Vercel Queues vs Workflow: which should I use?

Use Vercel Queues for background jobs, buffering, fan-out, and message routing. Use Vercel Workflow for durable multi-step business logic that needs retries, sleeps, or external event handling.

Does Vercel support WebSockets for realtime backends?

Yes, Vercel Functions with Fluid compute support bidirectional WebSocket connections without requiring a separate realtime service. This covers chat, live updates, and other realtime use cases.

How do I add a database to a Vercel backend?

Provision databases through Vercel Marketplace storage integrations, which inject credentials into your project automatically. Options include Postgres providers like Neon and Supabase, Redis via Upstash, MongoDB Atlas, and Turso for SQLite.

When should I use container images instead of native Vercel Functions?

Use container images when your 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.