[dead]
Ask HN: What would be your stack if you are building an MVP today?
21–30 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#22I would pick whichever stack that I would be most productive in.
A Laravel app hosted with Laravel Vapor (AWS Lambda) with a MariaDB database. Would allow me to get up and running quickly, at low cost and without having to worry about scaling for a long time.
Using Tailwind and VueJS or AlpineJS for the frontend.
Re: Ask HN: What would be your stack if you are building an MVP today?
#23My current go-to are:
1. Go (echo/gin) or Rust(actix/axum) (old-fashioned server-side rendered HTML)
2. alpine.js
3. htmx.org
4. tailwind
I've found that combination to give me amazing DX and appropriate speed of development.
Re: Ask HN: What would be your stack if you are building an MVP today?
#24I used NextJS and Firebase and while I disliked some of it: I would use it again because if the benefits of speed in building. With this setup you can permanently host for next to nothing until you get users, do zero devops or ops, and have something that will scale up (wont be the fastest thing but it will be OK and will scale) You could switch out NextJS for a static site generator too, but NextJS is pretty conveni…
I would not switch out NextJS for a SSG. NextJS can do SSG. But most SSG frameworks can't do SSR nor CSR.
Re: Ask HN: What would be your stack if you are building an MVP today?
#25Laravel. I don’t have time to fuck around with whatever the latest hotness is.
Re: Ask HN: What would be your stack if you are building an MVP today?
#26Django, in my previous role we did MVP websites for academics and the speed of getting a site up and running and deployed was just so fast. I’ve never worked with anything else that is as fast, anything like FastAPI or Flask or Express or similar either requires additional libraries to add really basic and common functionality or you have to roll it yourself. I personally don’t think that if you’re building an MVP yo…
Nowadays, Django has an amazing library which is a lot like FastAPI but in the Django ecosystem.
https://django-ninja.rest-framework.com/
It's absolutely wonderful. I would use that in a MVP, and do the F/E in NextJS + Typescript.
Re: Ask HN: What would be your stack if you are building an MVP today?
#27Directus connected to a Postgres database
Comes with a built-in low-config UI/API for CRUD on the database, and easily extendable with Vue.js and Express endpoints.
Additionally, should the need arise for something more custom later on, all your data is in Postgres rather than a backend as a service
Re: Ask HN: What would be your stack if you are building an MVP today?
#28- VPS like DO
- Server-side rendered app with Golang
- If interactivity is required: maybe Vue.js or jQuery
That's it.
Re: Ask HN: What would be your stack if you are building an MVP today?
#29Rails!
Re: Ask HN: What would be your stack if you are building an MVP today?
#30I've had an unparalleled experience in getting an MVP live with shuttle[0] - nothing is as fast for deploying a web app with a database to the cloud. For the database I’ve used shuttle’s dedicated SQL DB instance[1] and for the front-end I’ve used shuttle’s static file server[2].
If you are not scared of diving a bit into Rust, I'd a 100% recommend it.
[0] https://github.com/shuttle-hq/shuttle [1] https://docs.shuttle.rs/resources/shuttle-shared-db [2] https://docs.shuttle.rs/resources/shuttle-static-folder