[flagged]
Ask HN: What would be your stack if you are building an MVP today?
81–90 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#82Earlier quoted context omitted.
I‘m trying to learn Django just for this kind of MVP purposes. I also did a small mini project in RoR by following their documentation. Is there anything that is significantly easier to do in RoR vs. Django? Alternatively, is there anything, say, on a larger scale that I can do with RoR that I cannot do in Django if the project grows? These are the questions I‘ve been wrestling with quite a bit now. After learning Vu…
My view on this is that there is little between them so in that case it’s better to look at availability of skills you’d need to take it forwards in the operating region. For e.g. if it’s easier to hire Ruby developers then choose Rails. I see a lot of people talking about Elixir, etc. on this thread, but I’m based in the U.K. and I’ve never seen a company locally using Elixir so even if it’s really cool, it’d be a b…
Thank you for such a great and senseful answer!
Re: Ask HN: What would be your stack if you are building an MVP today?
#83Rails on postgres with React in the frontend is my default swiss army knife. I know Rails well and it still gets stuff done fast, comparatively speaking. If the problem space I work in requires something different or solves the problem better than Rails, I'd switch.
Edit: post-mvp, I'd stick with Rails still unless there are specific difficulties with it. But I've yet to have major issues building a large Rails team/project, including present day.
Re: Ask HN: What would be your stack if you are building an MVP today?
#84Backend: Rust + Axum/Tonic
Frontend: If webapp needed, Typescript + React. If just html templating, probably Yew
Database: PostgreSQL. Move to Yugabyte or Scylla if scale becomes needed.
Streaming/event driven architecture: Fluvio
Cloud: AWS
Servers: ECS/Fargate to start. Move to Kubernetes as needed
IaaC: CDK
Repository: Github Monorepo
CI/CD: Unsure.
Style: Monolith API server. Separations will be made through Rust modules and interfaces. For anything that requires dedicated CPU/threads, those will be moved to separate services to be called by the monolith via gRPC.
Re: Ask HN: What would be your stack if you are building an MVP today?
#85Personally 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, this is a non-issue: export types from db schema and all frontend requests are typed.
- Supabase is something for sure: I had been eyeing it for a while now, and it did not disappoint. Getting endpoints - even with realtime updates/subs in the frontend - after just defining a schema is magical.
- Auth is super simple with RLS - all this uses my SQL knowledge and makes me double down on it, which seems like a sane choice given it's been around for decades.
- Mantine gives me a large list of prebuilt components. This isn't exclusive to this stack but would highly recommend using something like this instead of just Bootstrap or Tailwind on its own.
Overall I'm happy with the results, feels way faster than my React/Rails workflow. Way less time in the backend (models, migrations, presenters, etc), more focus on tweaking the product.
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.
Re: Ask HN: What would be your stack if you are building an MVP today?
#86Earlier quoted context omitted.
I did so last year, and I cannot be happier. My only regret is that I wasn't aware of htmx/hotwire at the time. I went with Vue, and I regret it immensely. Rails is the fastest development platform I've tried so far, it is predictable, well crafted, structured yet flexible. You can't go wrong with it. Every now and then I try something new on a side project or I have to work on some other codebase for my customers, a…
I'm vaguely aware of htmx, but have never used it. Had not heard of hotwire until just now, but that looks really interesting. Thanks for the pointer! Would you care to say any more about your experience with Vue? I've heard a lot of good things about Vue and had it on my mental "things to learn one day" list for a while. Would be really interested in hearing any counter-points from somebody who hasn't enjoyed workin…
First I heard of HOTWIRE. I have been using PJAX for a decade now, which is a similar concept.
I use .net mvc with a razor templating engine. But this can be used with any backend.
It makes it super easy for me to maintain all my UX in server-rendered HTML templates. I get a clean SPA with super high development efficiency with MINIMAL javascript.
The best part was I could hire any developer and they know how to work in basic HTML/JS/CSS.
Edit: Reading more, I might need to spend time looking into HTMX/Hotwire as a replacement for PJAX at some point.
Re: Ask HN: What would be your stack if you are building an MVP today?
#87I've been writing Python for, gosh, almost 20 years now. I've used many frameworks but for an MVP I'd probably use good old web.py or Flask or similar.
Over those years I've come to greatly appreciate the wisdom of Gall's Law. I always start with an absurdly simple system, make damned sure it works, and only then complicate it.
Re: Ask HN: What would be your stack if you are building an MVP today?
#88I'm building an MVP solo. Rust for the core application, Elixir for the backend, frontend, API, data layer. Javascript is pretty much non-existent, all client-side interactivity is done by LiveView. Packaged into a podman container and deployed to a Hetzner dedicated server. Storage on PostgreSQL, probably the only thing I would rather not have to manage, but honestly single node is perfectly fine for an MVP. Provisi…
I love Rust and program in it a lot...but I would never use it for an MVP
Rust is the tool you use when you are done prototyping, not when you are just beginning
Re: Ask HN: What would be your stack if you are building an MVP today?
#89Linux VPS + C# + ASP NET Core If front needed then pure js or vue Database probably sqlite or postgres if that fits the needs
Similar to what I use.
I use .net mvc with a razor-templating engine. With pjax.
It makes it super easy for me to maintain all my UX in server-rendered HTML templates. I get a clean SPA with super high development efficiency with MINIMAL javascript.
Re: Ask HN: What would be your stack if you are building an MVP today?
#90janet, sqlite, and htmx.