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…
one thing I'd like to see in Django is something similar to InertiaJS [1], just being able to use VueJS for the view layer is amazing and passing data from the backend to the frontend without having to build complex api systems is a godsend. Maybe I haven't done enough research but is there something similar in Django world ? [1] https://inertiajs.com/
Ask HN: What would be your stack if you are building an MVP today?
721–730 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#722Developing in python for me is just much faster to get to a working prototype. Flask is super simple to use, and I find it great to implement HTTP REST APIs for the back-end of my MVP.
With Firebase you can deploy containers in the cloud and you don't pay until you reach a certain threshold of monthly requests.
In terms of my development environment I'd definitely use docker to containerize my environment and make it easier to collaborate with others. If I was making a bigger scale MVP with multiple collaborators and sensitive source code, I'd opt for a cloud based CDE (containerized development environment) with monitoring and security features, such as the one proposed by strong network.
Re: Ask HN: What would be your stack if you are building an MVP today?
#723Postgres and maybe Redis if I need a message queue or cache.
React for the front.
Nginx and certbot for the reverse proxy.
Everything hosted on a cheap OVH VPs.
Mostly because it's what I am familiar with. Plus it's cheap specially since I already have the VPs anyway.
Re: Ask HN: What would be your stack if you are building an MVP today?
#724When we were building the MVP for Transistor.fm, we chose Rails because it's what my co-founder knew the best.
These old-school web frameworks are mature, and still have a big ecosystem (community, resources, etc). Beyond Rails, we used AWS with Postgres, Redis, nginx/puma, and sidekiq for background jobs.
With any business (especially early stage), you only make progress when stuff gets built, deployed, and into the hands of customers. Remove anything that slows you down (like learning a new stack).
When we were in the MVP stage we recorded this podcast and went into more depth: https://saas.transistor.fm/episodes/nerd-stuff-our-web-app-t...
Re: Ask HN: What would be your stack if you are building an MVP today?
#725With clean conventions to start with.
From the get go, performance would be great, and it would be fairly easy to scale with azure container apps.
Than another week or so to polish things up. Most time from than would be U.I based.....
Just point of reference, a couple of weeks ago created .NET 7 Auth service creating JWT auth from AD B2C, along with custom X509 Cert in 2 days complete with docker image build using Azure KeyVault, another day to get build/deploy pipelines setup, plugging in Azure APIM.
It's really incredibly simple and fast to do now.
Re: Ask HN: What would be your stack if you are building an MVP today?
#726*Explanation:* >> I need to really push myself to finish my last YouTube MERN-stack tutorial. >> I will then be able to competently contribute to the planning and implementation of a real (full-stack-web, and mobile-native) app. —->>> Purpose of app: Higher-education advisory services for N.-American colleges, as well as international students and their sponsors.