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

201–210 of 736 posts

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

#201

Post by pc86 »

For the database, anything that's managed - I'm partial to SQL server just based on my work history, but Postgres is nice too. Even the expensive ones are like $100/mo for the lowest production tiers, if you're bootstrapping with a W2 job that's reasonable for 6 months while you try to find some level of traction.

For the backend, probably default to JS or maybe TS lambdas/function apps. Quick to write, quick to deploy, slap an API gateway over the top and you're ready to go.

For the front end, for a true POC I have a lifetime/full Creative Tim membership. So I'd just grab a dashboard and landing page template and start plugging in calls to the API gateway.

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

#202

Post by brookst »

FlyingSnake wrote: post #188
ultrasounder wrote: post #172

Definitely old schools. I am building a MVP right now(kinda building my parachute while jumping off the plane)and I went with Django. And here is why. 1. Very vibrant community of devs and time-tested open-source libraries.If you want a multi-tenancy there is a library for that. IF you want stripe integration there is one for that. If you want "fully built out" services, then we have a plethora of free and paid templ…

It’s funny that only in our industry “time tested”/“battle tested” is called old school and frowned upon. No wonder we see software bloat everywhere.

Eh, I think experimental physicists and medical imaging also lean towards newer tech.

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

#203

Post by taeric »

JohnBooty wrote: post #162
logifail wrote: post #108

> What would be your stack if you are building an MVP today? Many years ago a CIO told me he didn't really care what technologies I picked for an upcoming MVP backend, as long as I was already comfortable with them and would therefore be productive quickly. He also told me we would almost certainly need to rewrite everything at least once , so not to dwell too long on the initial stuff. Build the MVP, build it quickl…

He also told me we would almost certainly need to rewrite everything at least once, so not to dwell too long on the initial stuff. Build the MVP, build it quickly, get it in front of users. It just needs to work, you're not going to get marks, or customers, for backend coding style. 1000% agree. Overengineering things is the death of MVPs. But man this is hard to do in many real world situations. Stakeholders and man…

Agreed, but it is also easy to see the tension in your second paragraph. You can plan to rewrite everything at least once, but you will never get that actually in the plan.

My only somewhat clear path out of it is to make sure you built it so it will be easy to rewrite. Either do the least that you can, or keep an eye for improvements, but don't necessarily act on them.

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

#204

Post by leros »

I like using ExpressJS with Typescript and a Postgres database. There are lots of great hosting options, but I'm using Heroku right now.

I do really like the Firebase/Superbase options, but they impose restrictions and I don't like having restrictions like that unless I know for a fact that I'm building something very simple.

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

#205

Post by michaelteter »

jrvarela56 wrote: post #85

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

> Con: does not move me in the direction of using Python more. Feel like this is going to be a must-have for AI-powered components.

This is why too many companies build on Python... some thought that maybe someday they will need some AI something, and they hamstring themselves from the start with inferior tooling.

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

#206

Post by nicbou »

ultrasounder wrote: post #172

Definitely old schools. I am building a MVP right now(kinda building my parachute while jumping off the plane)and I went with Django. And here is why. 1. Very vibrant community of devs and time-tested open-source libraries.If you want a multi-tenancy there is a library for that. IF you want stripe integration there is one for that. If you want "fully built out" services, then we have a plethora of free and paid templ…

Agreed, although I'd really like to throw in type safety, because the lack of it made my life needlessly complicated. Is this feasible with Python?

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

#207

Post by eddieroger »

leros wrote: post #204

I like using ExpressJS with Typescript and a Postgres database. There are lots of great hosting options, but I'm using Heroku right now. I do really like the Firebase/Superbase options, but they impose restrictions and I don't like having restrictions like that unless I know for a fact that I'm building something very simple.

The Supabase folks are very active on here - if you shared your restrictions, maybe they'll open the up.

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

#208

Post by pc86 »

bob1029 wrote: post #196

.NET 7 & SQLite. Because I wouldn't need anything else. Also, it could potentially be my final stack depending on the size of my business & market. The current Kestrel web server implementation is extraordinarily fast (i.e. millions of requests per second fast). Vertical scaling isn't exactly a problem now that we have 2S servers with 256 cores (and beyond).

Have you found any good managed places to deploy modern .NET apps other than Azure? My experience is you can either use Azure, in which it's fairly abstracted for you but overpriced, or you can use something like DO where it's more reasonably priced but you have to handle everything yourself.

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

#209

Post by Supermancho »

The number of Elixir/Erlang backend suggestions seems over-represented. Not even Phoenix, just a blanket language suggestion. This leads me to believe that many posts are throwing out their newest stack-fad they imagine would be good for an application. I wouldn't take too much stock in the frequency of keywords here.

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

#210

Post by ch4s3 »

blascsi wrote: post #182

I've been trying to put together a solo project, that might be worth launching a bit later. My stack in general is: Elixir for the backend. Reasons for it: - Elixir is designed for reliability, so since I want to keep the app alive as much as I can by myself, it seems like a great fit. - It also has excellent integrations with Postgres (my choice of DB) with Ecto. - I generally skipped Phoenix, as I'm just using Elix…

> - I generally skipped Phoenix, as I'm just using Elixir to create my API.

Why specifically? Phoenix is mostly just some convenience on top of plug, but does a lot of things you'll have to reinvent.

Post reply on HN