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

501–510 of 736 posts

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

#501

Post by JeremyNT »

weaksauce wrote: post #444
foxandmouse wrote: post #319

Earlier quoted context omitted.

I'm glad I came across your comment, I'm planning a 2-week project for learning purposes and I thought rails backend with react/ svelte would be the fastest way to prototype. My ruby/ rails experience is very limited compared to my JS experience; I really just started experimenting with rails. I'm blown away by the magic, JS frameworks feel like toys in comparison. I also like that Rails is omakase. Based on your exp…

imo rails without react and leveraging hotwire is going to be the next big thing in web dev. react is a huge increase in complexity for not much appreciable gain. you are not facebook and don't have facebook's needs. rails is nimble by itself.

I'm a fan of this too, and it honestly confuses me that people would do a Rails API with React for a MVP.

If you're already doing the backend in rails, it's hardly any more work to just do hotwire with server side rendering at the same time, and you can switch to a SPA later (if you really do need to).

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

#502

Post by dimgl »

tdy721 wrote: post #290
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...

For good reason.

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

#504

Post by moltar »

sourdesi wrote: post #404

I’ve been working on a side project that aims to provide a really simple UX to spin up full-stack web apps with CI and scalable infra by default. The idea is that you would simply enter a domain name you want to purchase and then the tool would do the following: 1. Purchase the domain name using AWS Route53 (perhaps you’d need to setup an IAM role for the website to access your pre existing AWS acct) 2. Setup fronten…

Hey sourdesi, this is _exactly_ my stack too, and I am also dabbling with a starter. Would also love to discuss and collaborate. Please send me an email (see profile).

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

#505

Post by 0xblinq »

Rastonbury wrote: post #297
0xblinq wrote: post #257

Earlier quoted context omitted.

This stack is pretty incomplete for most MVPs, as unless you're building something trivial like a landing page, you'll probably at some point also need libraries or a custom implementation for: - Validations - Translations - 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 - Bac…

That stuff isn't "hard" per se, and some of that stuff isn't even needed for a MVP, they're good to haves or only really required when you've got 100s of users (product dependant of course). If the MVP doesn't get there either iterate product or bin it

None of these are difficult per se. Multiple of them, working seamlessly together, having them tested, documented and battle tested is a bit more difficult.

Then you think about all that time doing this could have been spent in actual business logic and it makes no sense to me anymore.

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

#507

Post by fatih-erikli »

NextJS/Typescript. For the database, maybe Redis, or Mongodb. RDMS except sqlite seem to be overkill for an MVP.

For frontend, a picocss-like minimal framework.

Django for the next stage. It's good for blogs, feedback management, back-office. Django beats rails. Rails is generating (scaffold) code while Django abstracting the CRUD operations. Clever abstraction beats generated code.

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

#508

Post by Towaway69 »

petercooper wrote: post #485
Towaway69 wrote: post #398

I recently built a Web based MVP and used Node-Red as backend. Frontend was python+flask, postgres and everything dockerized. I've mainly used sinatra and rails for Web apps and always found it difficult to define a clear api on which the frontend was based on (I.e in order later to build ios or android apps off). Using Node-Red forced me to build an api for the frontend, the frontend has no direct contact with postg…

There is so little out there about using Node-Red in this way that I would certainly love to see a writeup of the experience if ever you fancy it!

My experience also! It seems NR is only used for IoT and hobby projects but it definitely has more potential.

What I use it for is api endpoint, email templates and sending emails, websockets and as admin tool (the dashboard).

It requires a lot of discipline to keep the flows separate. Reuse of code is a challenge (very tempting just to copy and paste code) and generally to maintaining an overview (simply because of the number of flows).

On the other hand, business people can immediately see the flows and thereby understand the logic. Debugging is a matter of connecting a debug node at any point in flow. Background jobs (ie sending email) is a matter of splitting the output of a node (ie http response is sent and at the same time email is triggered or websocket update is sent).

Scalability and production performance remains an open question for me. In worse case scenario it would be a case of taking the flow.json (my entire backend is a 300k json) and building some kind of interpretor from scratch ;)

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

#509

Post by maxcan »

Data: Postgres & Hasura (for me Hasura is the goldilocks level of abstraction - lets me skip writing CRUD handlers, but doesn't get in the way either when I need to do something complex).

Frontend: TypeScript, React, apollo client, graphql-code-generator, tailwind

Backend Logic: Lambda functions written in TS, packaged with serverless.com, but deployed with Terraform

CI: GH Actions

Deployment: AWS via Terraform. One account per environment under an umbrella org.

Because I've used this stack so many times I can get a "shovel ready" foundation going in minutes with a skeleton that I've been iterating on.

Post reply on HN