Frontend, backend, database, hosting how to decide what to use without over‑engineering?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Hey James, Start with what you know and what your team knows; familiarity usually beats hype. For a typical web app, pick one mature frontend framework (React, Vue, or Svelte) and one backend language you’re comfortable with (Node.js, Python, or Go). Choose a simple, reliable database (PostgreSQL or MongoDB) and a straightforward hosting option (Vercel/Netlify for frontend, a basic cloud VM or managed service for backend). Avoid adding extra tools until you actually need them.
Ask three questions: What problem are you solving? Who is your audience? What are your constraints? If it’s a small MVP, go for simple, opinionated stacks (e.g., Next.js + Node + PostgreSQL) so you ship fast. If you expect heavy traffic or complex data, prioritize scalability and observability early. Document your stack decisions and revisit them every few months; your “right” stack will evolve as your app and team grow.