What problem does it solve? Choosing the right backend architecture on Vercel is difficult because workloads span HTTP APIs, WebSockets, background jobs, durable workflows, containers, and databases, each mapping to a different product. This Skill guides architecture selection from the workload first, before any implementation details. ## Core Features & Use Cases - Product Mapping: Matches workload types (HTTP APIs, WebSockets, cron, background jobs, durable multi-step logic) to Vercel Functions, Services, Queues, Workflow, Cron Jobs, and Blob. - Framework Selection: Covers supported backend frameworks including Express, Fastify, Hono, NestJS, Next.js Route Handlers, FastAPI, Flask, Django, and Go. - Database Provisioning: Directs Postgres, Redis, MongoDB, SQLite, and analytics storage choices through Vercel Marketplace integrations with injected credentials. - Use Case: A developer with an existing Dockerfile and a FastAPI service uses this Skill to decide between container images on Functions versus Services, then provisions Neon Postgres via the Marketplace. ## Quick Start Ask the assistant to plan a backend on Vercel for your API, background jobs, and database using the create-a-backend skill.