Infrastructure Service Defaults

Selecting infrastructure services for Next.js involves mapping specific needs like caching and storage to existing stack components. This skill provides a decision table recommending Vercel, Supabase, and Upstash to minimize unnecessary service additions and streamline architecture.

The best way to handle job queues and real-time updates in a Next.js Vercel stack is using existing services. The skill recommends using QStash for job queues and Supabase Realtime for live updates, avoiding the addition of extra services.

You do not need a fourth service for analytics if you already use Vercel, Supabase, and Upstash. The skill's decision table guides you to leverage these existing stack components for analytics and other infrastructure concerns unless justified.

The infrastructure service decision table works by matching specific Next.js project requirements like caching and storage to recommended existing services. It details Vercel, Supabase, and Upstash use cases to minimize architectural complexity and streamline development team decisions.

You should not use existing stack services for infrastructure needs in Next.js only when adding a fourth service is explicitly justified by project requirements. The skill is designed to minimize service sprawl by prioritizing Vercel, Supabase, and Upstash for common tasks.