Clojure's not the easiest thing to get into, the stability and documentation and libraries are great.
Ask HN: What would be your stack if you are building an MVP today?
181–190 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#182Elixir 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?
#183Re: Ask HN: What would be your stack if you are building an MVP today?
#184C# REST APIs on Linux with PostgreSQL and the front-end framework of your choice. I generally stick with Angular.
Re: Ask HN: What would be your stack if you are building an MVP today?
#185As somebody trying to learn the web stack, reading this thread makes me a little sick to my stomach. Edit: Thanks for the advice!
Re: Ask HN: What would be your stack if you are building an MVP today?
#186Re: Ask HN: What would be your stack if you are building an MVP today?
#187Until 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?
#188Definitely 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…
Re: Ask HN: What would be your stack if you are building an MVP today?
#189But 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.