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

471–480 of 736 posts

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

#471

Post by DwnVoteHoneyPot »

jononomo wrote: post #399
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 Django Book is phenomenal. It is just so well-written and so clear that it makes my heart ache: https://django-book.readthedocs.io/en/latest/introduction.ht...

Another good one is Tango with Django. https://www.tangowithdjango.com/

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

#473

Post by ajjenkins »

I agree with that too comments that you should avoid having a backend at all for your MVP if you can avoid it (just make a static hosted website with HTML, CSS, and minimal JS).

But since you asked about backends specifically, this is what I would use. I would use clerk.dev for authentication, Hasura for the CRUD API, neon.tech for the database, S3 for static files (images), and AWS Lambda for any extra functionality you can’t accomplish with Hasura natively (but call them through Hasura).

Personally, I like using GraphQL because I can just focus on my data model and not think about what endpoints I need to make. But there’s definitely a learning curve, so sticking with a REST API is probably better for most people.

As an alternative, I would also consider Supabase like you mentioned. It sounds cool, but I’m already comfortable with Hasura so that’s what I go to first.

Update: For a website, I would actually use Remix with Clerk for auth and Prisma/SQLite for data stuff. That’s one of their premade starter stacks. I made one prototype with Remix and had a lot of fun using it. It’s easy to learn and will give you a high performance full stack app. My original answer is what I would use if you’re making a mobile app.

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

#474

Post by shpx »

skizm wrote: post #368

HTML, css, js, (maybe jquery and font-awesome if I want to get fancy) and all static files dumped in an S3 bucket for as long as I can get away with it, then django if I need anything more. Not that I think python/django is the "best", but it is what I know and it's got all the batteries included out of the box. I've never made a sufficiently advanced UI that required react/vue/etc. So I still just stick with html/cs…

Instead of an S3 bucket you can use GitHub Pages. You push stuff to the upstream git repo and it gets deployed. It’s free (you have to pay for GitHub Pro if you don’t want to make the source code publicly available) and comes with Fastly CDN if I recall correctly. You just have to configure your custom domain.

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

#475

Post by noveltyaccount »

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…

IMO for early stage startups, proven tech is almost always a better bet than the hot new thing. Your goal is to capture market share quickly, not wrangle beta tech into place.

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

#477

Post by bradwood »

bradwood wrote: post #472

AWS Serverless -- all day long... Lambda, DynamoDB, API G/W, SNS/SQS, EventBridge, S3, Cloudfront. Reasons: no servers, no VPCs, no k8s yaml, great tooling, easy to deploy (serverless framework, terraform, etc), easy to secure.

oh, and extremely cheap.

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

#478

Post by gregjotau »

- Spring boot (Java 19)

- HTMX + Thymeleaf (replacing need for any SPA framework)

- Bootstrap

- Vanilla JS when needed

- Postgres

- Deploy on Ubuntu server with a deploy.sh that just does cd => git pull => gradlew build => systemctl restart X.service :)

Why? I have been convinced that most web application can and should be created without JS frameworks :P

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

#479

Post by noveltyaccount »

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…

This is excellent advice. The "worse is better" manifesto says similarly:

> The lesson to be learned from this is that it is often undesirable to go for the right thing first. It is better to get half of the right thing available so that it spreads.

https://www.dreamsongs.com/RiseOfWorseIsBetter.html

Post reply on HN