Nodejs plus plain sql Postgres
I used to use Django as a first choice but nodejs/sql is much simpler.
React in front end.
Linux server running Caddy.
Ask HN: What would be your stack if you are building an MVP today?
321–330 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#322There is only one good answer to that, you should use what you already know, if you build an MVP it's to deliver a product, it's not meant to spend 2-3x more time to learn new tech.
This is always the wrong answer to this question.
Yet it never goes out of style, apparently.
Re: Ask HN: What would be your stack if you are building an MVP today?
#323Java and Postgres. For large numbers of devs, this is a very intuitive stack they have lots of experience in and can get work done super quick. Also won’t have to rewrite later because good performance. I’d stay away from depending on any vendors for anything except a VM to bring your servlet container up on.
Re: Ask HN: What would be your stack if you are building an MVP today?
#324Maybe the standard Node and React on the front end?
Tried too many niche languages and technologies and now I always come back to JS to stick to the same platform for everything
Re: Ask HN: What would be your stack if you are building an MVP today?
#325.net core on whatever is the simplest to get it to production.
99% of your projects do not need hyper scale and you are just engineering problems for yourself.
Re: Ask HN: What would be your stack if you are building an MVP today?
#326I'm 90% on Ruby on Rails dockerized. Meaning I would almost certainly choose that absent a very good reason to use some other backend stack. Rails because it's highly battle tested and flexible and good enough for almost anything. Dockerized because IME setting up and maintaining a Ruby environment with up to date version on bare metal is highly painful. Docker lets me be much more consistent with both Ruby versions and the rest of the server config.
I'm less solid on the deployment. Could go with one of the commercial docker-y hosting systems, or a commercial K8s setup, or a hand-rolled Docker host via Ansible. I've done all 3, and I'm not sold on any of them being the best for everything.
Front-end side is more flexible depending on the type of site/business. Normal ERB-style SSR is probably fine for a lot of things with a few sprinkles of basic JS. Would re-explore if I thought it needed a proper front-end app. React is neat, but darned if every single time I try to do a version bump on a small React app, I end up needing to rewrite half of it.
Re: Ask HN: What would be your stack if you are building an MVP today?
#327full a full stack web app
Backend:
Postgres
Go
Frontend:
Typescript React, with React Query
Tailwind for styles
Why? Because i know these technologies fairly well.
Re: Ask HN: What would be your stack if you are building an MVP today?
#328Frontend: React + React Query. Backend: * Java Spring if it looks like monolith. * Golang if it looks like microservice architecture. Postgres for data. S3 for blobs. RabbitMQ for queues. Kubernetes for infrastructure. Managed or self-hosted, doesn't matter. One 16GB VPS is good enough for start and can be scaled later. That's my approach to any architecture today.
you and i have a pretty similar preference!
Re: Ask HN: What would be your stack if you are building an MVP today?
#329Personally big on Rails (use it at work every day). But, my last MVP I did with TS/Next/Mantine/Supabase/Vercel. Reasons: - I've been using Rails as an API only, so having to grok views felt like a waste. My React skills made me feel that learning how to make complex views in my backend was a waste of time. - One type of bug I hate is ensuring my API calls have the right schema. With Supabase and TS in the frontend,…
I'm glad I came across your comment, I'm planning a 2-week project for learning purposes and I thought rails backend with react/ svelte would be the fastest way to prototype. My ruby/ rails experience is very limited compared to my JS experience; I really just started experimenting with rails. I'm blown away by the magic, JS frameworks feel like toys in comparison. I also like that Rails is omakase. Based on your exp…
I was faced with this decision a month ago and started building my models and views in Rails 7. Late night tinkering with views, then trying out ViewComponent I went 'dude wtf am I doing, these apps are so easy to build in React'... Next.js with Supabase has been a breeze. Setting up db with auth and getting realtime updates and object storage with minimal setup (TS fn calls) was mind-blowing.
Caveats: setting up Supabase auth takes a bit of reading docs, using the js helpers correctly and configuring RLS, but after that it just works.
Re: Ask HN: What would be your stack if you are building an MVP today?
#330Django-Ninja but in Lambda with an RDS Postgres backend and a Vue/TS frontend. Why? Because it's what I know. It's on my agenda to learn more about Elixir. I think it really depends on what the MVP is for!