T3 (https://create.t3.gg/) + Postgres (RDS). Hosted on AWS, Node Lambdas for async / background work.
Ask HN: What would be your stack if you are building an MVP today?
71–80 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#72elixir/phoenix is the best platform for knocking out an MVP today. Its batteries included and has a frontend system called liveview that lets you write most of your frontend using elixir too. You get built in pubsub and websockets which are important for any new kind of software product. Users demand more interactivity and phoenix lets you do it and scale from day 1. Ecto is easily the best sql database library I've…
Holy smokes! I had no idea this project existed, and it just solves so many issues out of the box.
I'm a backend/infra developer, and I had been dreading having to learn a new front end framework because the work flows just look hideous. This looks like I can sidestep most of that problem entirely.
Re: Ask HN: What would be your stack if you are building an MVP today?
#73You can build basically any MVP in almost any programming language and platform.
That said, anybody who gives an answer without knowing what they're building first and knowing the tradeoffs involved IMO isn't doing things right.
Re: Ask HN: What would be your stack if you are building an MVP today?
#74Remix Run
Re: Ask HN: What would be your stack if you are building an MVP today?
#75Front end: TypeScript, Vite, React, FontAwesome, Radix UI, lodash, React Router, zod, SCSS.
Back end: Python, mypy, Django, Django REST Framework, Celery, Redis, PostgreSQL
Re: Ask HN: What would be your stack if you are building an MVP today?
#76Earlier quoted context omitted.
This. Your fastest stack is not my fastest stack. If you want to learn the ‘fastest’ frameworks, that is a totally different decision than getting an MVP out the door. That is an educational one… which is totally valid just not in an MVP sense. The goal of the MVP is ascertaining product market fit, everything else is waste. Use what you know and optimize later. If your MVP can handle 1m calls a second, you have fail…
I think it's a very reductive view. One cannot try every stack to find its fastest stack. This is why people ask about other people's experiences. Someone might have a better solution, and a convincing argument, so you could try it and become more productive.
I have a relatively terrible answer that I would recommend to no one but it works for me. That's the fastest stack for me.
The question wasn't "what is the fastest stack" or "of all stacks which is the fastest for you" but rather akin to "what is the fastest stack for you". Which is often the one that you are productive in.
It's almost always not worth learning a new stack to prototype something unless the goal is to learn the new stack.
Re: Ask HN: What would be your stack if you are building an MVP today?
#77For an MVP, I'd choose what I'm most familiar with and can be fastest with. That would mean:
1. Laravel
2. An Ubuntu VPS in either Digital Ocean or Linode
3. A managed database in one of those services, likely Postgres
That would get me to market the quickest. I have no issues with the application being in Laravel/PHP and after getting to market, I'd work on making the infrastructure scalable. I wouldn't expect overnight success, so a single VPS and managed database would let me keep costs low while I pick up a few customers and then work to handle the scalability in the background (likely AWS with a combination of EC2/ECS/Fargate, RDS, SQS, SES, CodeDeploy, ElastiCache, etc.)
Re: Ask HN: What would be your stack if you are building an MVP today?
#78I'd use Postgres for the data layer, I'd build the service layer around OpenFAAS (using faasd) and Node/Typescript functions, and for the client I'd probably go with React/Next (though Svelte is starting to look pretty attractive). For basic CRUD functions I would probably use Postgrest.
I'd stand it up on a VPS initially, using ansible scripts to make switching deployment targets to AWS easy.
Re: Ask HN: What would be your stack if you are building an MVP today?
#79I could explain what I'd choose, but that's irrelevant as it's based on my existing skills
The one thing I can't recommend enough is the value of organizing persistence around a nosql distributed db and blobs of zipped files (also distributed)
In my experience, db is expensive. But this setup is dirt cheap.
Sqlite is good but it makes you worry about scaling (so it's great for an MVP)
Re: Ask HN: What would be your stack if you are building an MVP today?
#80If you are already using postgres, then postgrest for backend, and solidJS for front end.