What problem does it solve? Choosing the right backend architecture on Vercel is confusing when you must decide between Functions, Services, container images, Queues, Workflow, and Marketplace databases. This Skill guides that decision from the workload outward, so you pick products and frameworks before writing implementation code. ## Core Features & Use Cases - Product Mapping: Matches workload types (HTTP APIs, WebSockets, background jobs, durable multi-step logic, scheduled tasks) to the correct Vercel product such as Functions with Fluid compute, Services, Queues, Workflow, or Cron Jobs. - Database Selection: Recommends Marketplace storage integrations (Neon, Supabase, Upstash, MongoDB Atlas, Turso, and more) with guidance on regions and serverless-compatible connections. - Framework Guidance: Covers supported backend frameworks including Express, Fastify, Hono, NestJS, FastAPI, Flask, Django, and Go, plus container images for custom runtimes. - Use Case: You have a Next.js frontend and a FastAPI service with background jobs. Use this Skill to decide between Services and separate projects, pick Queues versus Workflow for the jobs, and select a Postgres provider before deploying. ## Quick Start Use the create-a-backend skill to plan the architecture for deploying my FastAPI backend with a Postgres database on Vercel.
