Tech Stack Picker
What it is: Tech selection: before writing code, figure out which frontend, backend, database and middleware to use. Combine them freely here and understand each at a glance.
When to use: When you want to build something but don't know what tech to use, or want to grasp what Kafka/Redis actually do.
Hover any technology on the left to instantly see what it is and whether it is still popular in 2026. Click to add it to your stack — the panel then tells you what kind of project the combination suits and what to watch out for.
Not sure where to start? Apply a stack by project type
Pick the kind of project you want to build to auto-fill a recommended stack, then tweak it below.
Frontend
requiredBackend
requiredDatabase
optionalDev Toolchain
multi-selectConfig / Infra
multi-selectHover any technology on the left — its full description appears here instantly. Click to add it to your stack.
Once you pick a frontend and backend, this tells you what kind of project it suits.
Everything runs locally in your browser — nothing is uploaded.
FAQ
Do the frontend and backend frameworks have to be used as a pair?
Not necessarily. They can be fully independent (e.g. a React frontend + a Java backend talking over an API), which is the most flexible; or a full-stack framework like Next.js or Django can do both. If you want the least hassle, start with a full-stack framework or a BaaS like Supabase.
When do you actually need Kafka or a message queue?
Only when you have slow tasks that need not return immediately (sending email, generating reports, post-order processing), or need to pass large volumes of events asynchronously between services. RabbitMQ is enough at small/mid scale; Kafka is for massive event streams (logs, analytics, big-data pipelines). You rarely need it early — do not adopt it prematurely.
Can SQLite be used in production?
Yes. For read-heavy, low-concurrency small/mid sites, SQLite is stable and zero-ops, and can even go distributed with Turso/LiteFS. Only genuinely high-write, high-concurrency systems need to move to PostgreSQL/MySQL.
Should I treat this tool’s recommendation as the definitive answer?
It gives directional guidance based on mainstream practice, to help you quickly grasp where each technology fits and how they pair. Real decisions also depend on your team’s existing skills, hiring, budget and requirements — often the best stack is simply the one your team knows best.