Cheat sheet maps modern stacks to projects

Two developer posts are getting passed around as shorthand for a familiar problem: picking a stack for a portfolio app without turning the choice into a six-month research project. One maps common jobs to tools; the other lays out a step-by-step full-stack path. (x.com 1) (x.com 2) The first post uses an “if it’s…” format: WebSockets for live updates, Apache Kafka for high-volume event streams, React or Next.js for frontends, and Kubernetes for running containerized apps across clusters. The second post, shared by student developer Gourav Saha, lists a learning order from Next.js to Prisma and Postgres, then Auth.js and Zod, then Vitest, Playwright, pnpm, Turborepo, and Docker. (x.com 1) (x.com 2) A stack is the bundle of tools used to build and run an app: interface, server code, database, login, testing, packaging, and deployment. These posts reduce that bundle to a menu of common tradeoffs, which is part of why they are circulating beyond the people who wrote them. (nextjs.org) (prisma.io) (kubernetes.io) The tools in the cheat sheet solve different kinds of problems. WebSockets keep a browser and server connected so messages can move both ways without repeated polling, Kafka is built for event streaming from many producers to many consumers, and Kubernetes automates deployment, scaling, and management for containerized applications. (developer.mozilla.org) (kafka.apache.org) (kubernetes.io) The student roadmap is narrower and more opinionated. Next.js is a React framework for full-stack web apps, Prisma is an object-relational mapper that gives typed database access, and Prisma’s own guides pair that setup with Postgres and Auth.js for login flows in a single app. (nextjs.org) (prisma.io 1) (prisma.io 2) (authjs.dev) The rest of that path covers guardrails and workflow. Zod is commonly used for schema validation in TypeScript projects, Vitest handles unit tests, Playwright runs browser tests across Chromium, Firefox, and WebKit, and pnpm and Turborepo are pitched as faster ways to manage dependencies and builds as projects grow. (x.com) (vitest.dev) (playwright.dev) (pnpm.io) (turborepo.dev) The appeal of both posts is that they favor “good enough for this project” over “best tool in the abstract.” Prisma publishes a Next.js guide, Vercel publishes a Next.js-Prisma-Postgres walkthrough, and GitHub hosts starter repos that package those choices into something a student can ship and show. (prisma.io) (vercel.com) (github.com) That does not make the lists universal. Kafka and Kubernetes add operational overhead that many small portfolio apps do not need, while a single Next.js app with a Postgres database and basic authentication can cover dashboards, marketplaces, booking tools, and internal admin panels without introducing distributed systems from day one. (kafka.apache.org) (kubernetes.io) (nextjs.org) The thread running through both posts is less about brand names than about fit: choose the simplest tool that matches the job, then add heavier machinery when the project actually demands it. That is a cleaner story for a portfolio than a stack chosen to impress strangers on the internet. (x.com) (x.com)