Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What would be your stack if you are building an MVP today?

news.ycombinator.com

Post reply on HN
Print view View original

281–290 of 736 posts

Re: Ask HN: What would be your stack if you are building an MVP today?

#281

Post by dbbk »

turadg wrote: post #165

I'm surprised nobody has mentioned https://redwoodjs.com Here's why I'd pick it: 1. One language for the whole stack. It's an MVP so the front and back are both changing fast, with changes made by the same person, and you don't want to context switch all the time. 1a. Javascript as that language because it's the most flexible. And with TypeScript you can gradually opt into type constraints where they help you. 2. An…

I've never been much a fan of Node for backends though. There's no framework that's as feature packed as, for example, Laravel on PHP. And you have to worry about leaking state/memory across requests.

Re: Ask HN: What would be your stack if you are building an MVP today?

#282

Post by 0xblinq »

turadg wrote: post #165

I'm surprised nobody has mentioned https://redwoodjs.com Here's why I'd pick it: 1. One language for the whole stack. It's an MVP so the front and back are both changing fast, with changes made by the same person, and you don't want to context switch all the time. 1a. Javascript as that language because it's the most flexible. And with TypeScript you can gradually opt into type constraints where they help you. 2. An…

None of these frameworks (next.js, remix, redwood, etc, etc, etc) is a even half close to what you need for any non-trivial MVP backend. Such as:

- Validations

- Translations/localization

- Error and request logging and auditing

- Security (CQRS, CORS, CSRF)

- Permissions and a way to integrate it with your authentication (does supabase handle this? don't know)

- Email sending

- Background jobs

- Caching

- File uploading

- Rate limiting

Several of these very important things are missing for all of these frameworks. While most of them come by default or with community maintained "de facto" solutions.

I'm yet to see a feature wise equivalent framework in the JS world to laravel/django/rails. They're batteries included or full stack just on the surface, as soon as you start using them you start missing a ton of stuff.

Re: Ask HN: What would be your stack if you are building an MVP today?

#283

Post by danudey »

bastawhiz wrote: post #133
physicsguy wrote: post #15

Django, 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…

The biggest benefit to Django, in my opinion, is the orm and admin tooling. Being able to fix things in your app without having to open a repl or open a database tool is absolutely killer.

I honestly cannot believe that Rails doesn't have this built in. This was something that was in Django for as long as I can remember; I was looking at it in I think 2006 and it existed at that point in a very similar state to what I've seen lately.

Not a dig on Rails, like "Oh, Rails is so bad they don't even have..."; rather, Rails is extremely capable, and so are Rails devs, so I legitimately don't understand why this isn't there already, 15+ years after Django.

Re: Ask HN: What would be your stack if you are building an MVP today?

#284

Post by iwebdevfromhome »

While I prefer python for everything else, I'd go with Laravel Jetstream[1] for an MVP, just like I did with the last one I had to build. It's laravel, you can use Vue (React or Svelte) for your views instead of the blade templating language that comes with the framework. Jetstream also comes with Auth, user login and subscription and other useful stuff.

And for the flavor, I'd just go with DaisyUI[2] again, since it's based on tailwindcss and it's what I've been using lately.

In my experience, I can build MVPs real fast with the stack described above.

[1] https://jetstream.laravel.com [2] https://daisyui.com/

Re: Ask HN: What would be your stack if you are building an MVP today?

#285

Post by adam_gyroscope »

I'd do python + django + bit.io (serverless postgres; I'm the CEO but I built it because I wanted to use it), deployed in a container to k8s somewhere. These are all personal biases to what I've used and know well; for someone new to backend I'd probably recommend next.js + nodepg + bit.io on vercel or similar.

Re: Ask HN: What would be your stack if you are building an MVP today?

#286

Post by itpragmatik »

itpragmatik wrote: post #125

- Backend: Java - Front end: React - Persistence: MySQL and S3 - Dockerize containers for backend and front end - AWS CodeCommit for code repo - AWS CodeBuild and CodeDeploy for CI/CD - AWS ECS Fargate

Java aka Spring Boot 3.x

Re: Ask HN: What would be your stack if you are building an MVP today?

#287

Post by RussianCow »

shireboy wrote: post #261
thecodemonkey wrote: post #22

I 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.

That’s usually my take, but I still worry about a few things: * which stack will still be around in 1/2/5years? * which stack Will other teammates or future devs be productive in. I’m still searching for a very light, productive open source stack that is well accepted and if not future proof at least we’ll backed.

For an MVP, none of those things matter. Just rewrite it in a different stack later if you realize that the one you picked doesn't fit your requirements long-term. Worrying about that stuff before you have users/customers is just a waste of time and energy.

Re: Ask HN: What would be your stack if you are building an MVP today?

#288

Post by kiwicopple »

Hortinstein wrote: post #12
v3ss0n wrote: post #10

Supabase is very resource intensive. Django+drf+ spectacular+filters+jwt gives you all the perks of supabase with - much easier syntax - much lighter weight - alot higher productivity - UI auto generation

I am curious to know more, can you point me in the direction of any blog posts outlining this stack? I have been using supabase for a few months and for local dev it is pretty heavy

> for local dev it is pretty heavy

We were discussing this in our CLI catchup this morning. It seems the Dashboard/Studio is the main culprit here. We'll fix it

Re: Ask HN: What would be your stack if you are building an MVP today?

#290

Post by tdy721 »

v3ss0n wrote: post #215

Hhere is quick survey : Regarding backend choices: curl "https://news.ycombinator.com/item?id=34530052" | grep -i Django | wc -l 36 curl "https://news.ycombinator.com/item?id=34530052" | grep -i supabase | wc -l 17 curl "https://news.ycombinator.com/item?id=34530052" | grep -i rails | wc -l 28 curl "https://news.ycombinator.com/item?id=34530052" | grep -i node | wc -l 15 curl "https://news.ycombinator.com/item?id=345…

Deno didnt make the list...
Post reply on HN