Live data from Hacker News

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

news.ycombinator.com

181–190 of 736 posts

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

#181
I am building one now as a single founder, with plans to never grow beyond a few people, and I'm using Clojure + Postgres (having done Python for almost 20 years!). I do technical due diligence for private equity companies for a living, and I evaluated two Clojure companies. It was amazing how much they could avoid in terms of problems as a small team by leveraging the JVMs concurrency and threading capabilities. No worrying about microservices, managing crazy k8 systems, or complex CQRS problems, no outgrowing pokey ORMs (a problem I have talked to way too many mid stage companies about who started on Rails or Django - huge elephant in the room there). I intend to use a mix of HTMX, some Reframe (a clojurescript reactive framework over react) and webassembly on the front end.

Clojure's not the easiest thing to get into, the stability and documentation and libraries are great.

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

#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 Elixir to create my API.

- Absinthe provides amazing support to create GraphQL API from scratch.

Frontend will be React probably with Relay.

- I've been using React at my job for years with GraphQL and I'm pretty fond of it.

- I've been planning on investingating Mobx, as I've never used it but heard good things about performance there. I'm not sure if it's going to be worth using it with GraphQL

- Relay has quite a lot of boilerplate, but I found it good enough for what I'm doing, and I liked the performance. Also it's fairly easy to integrate with Absinthe.

- Generally since this project is not made to be a start up or a business first, I want to experiment on the front-end on how I could reach the best performance with these tools at hand.

- I plan on using TS with the GraphQL queries mostly generated from the schema.

For deployment I plan on using a VPS probably, though I'm way far from having to choose that.

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

#185

As somebody trying to learn the web stack, reading this thread makes me a little sick to my stomach. Edit: Thanks for the advice!

They're all basically the same, some are just more or less bad and some have more or fewer very-helpful libraries available. It's all doing the same shit, mostly in very similar ways.

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

#187
These days with Hotwire and HTMX, you can go very far with Django/Rails (and I suppose Elixir too). Not having to write an API for your webapp to consume is huge.

Until you actually have reason to scale (eg you are building WhatsApp), building to optimize the productivity of your iteration cycle usually gives the best payoff for pre-PMF projects.

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

#188

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.

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

#189
Depends on the project.

But in general:

* Old School VPS or Cloudflare Workers (if the problem lends itself well to Workers)

* Usually leaning towards sqlite instead of a hosted postgres (as that's often overkill)

* Language: whatever fits the problem best. These days likely TypeScript as it's so versatile.

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

#190
You mean specifically for products that involve the internet/web and is "full stack"? I'm not very familiar with the trends there but I do know I'd likely use a whole different toolset if I was only building a service without web frontend than if it had a web frontend. And whether or not it involves a database of some kind (and what kind) also heavily influences the choice of tools and platforms.
Post reply on HN