Ask HN: What would be your stack if you are building an MVP today?
271–280 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#272Main reasons are:
- Can build entire app (with SPA-type experience on the FE) in a single codebase
- No need to build any HTTP APIs
- Periodic tasks and managing in-memory state is super easy in Elixir. Eventually you might want to stick state somewhere which survives restarts (eg redis) but for the sake of moving quickly Elixir makes this really easy
- Newer versions of Phoenix/LiveView support html components so building out UIs now feels as nice as some of the tools in the FE ecosystem
Re: Ask HN: What would be your stack if you are building an MVP today?
#273I think I'd have to say NextJS with SQLite. Every DB table would just be 'id' and 'data', where 'data' is JSON-encoded and the schema is only enforced in code. This lets you write a 30-line ORM. Foreign-key relationships are just modelled as lists. If speed is the major concern, I find this the fastest way to build. You can bring structure to the DB as things are nailed down.
Re: Ask HN: What would be your stack if you are building an MVP today?
#274Definitely 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?
#275I suck at UI/UX design and don't want to write a bunch of JS for async webapp stuff, so retool is a force multiplier there and would highly recommend. I Don't want to manage any infra, so appengine handles that for me. After getting everything setup with terraform in a day or so, I spend all of my time developing core functionality and 0 time managing servers or getting a UI to do what I want it to do.
Total cost to host is < $100
Re: Ask HN: What would be your stack if you are building an MVP today?
#276Go & Postgres on the backend, running on a baremetal server. Because this is actually capable of handling a decent workload for really cheap compared to cloud. There's a few tricky bits to do with logs and reporting, but the benefits outweigh the pain. Vue on the frontend. Last time I used BootstrapVue and it worked well. I'd want to re-evaluate that decision next time, have a look at some of the newcomers. I'm aware…
You should take a look at Vite (https://vitejs.dev/) for a Vue development environment, if you haven't already.
Re: Ask HN: What would be your stack if you are building an MVP today?
#277Earlier quoted context omitted.
I think we need to be super precise when we use the word "managed". Today, we use EC2/Azure VMs to run a lot of .NET 6+ apps. I consider these to be managed resources. My involvement with those servers is an email from the hypervisor ~once a year politely requesting a reboot. I don't think .NET has any specific implications regarding where the product is hosted. If you are referring to the Microsoft insight/Azure int…
That's basically what I mean. I just want to deploy the app and not have to worry about anything OS-related, including IIS config, SSL, etc.
The management of certificates, configuration, etc. is built directly into any product I work on. Outsourcing this stuff to IIS, et. al. is exactly how you wind up hating all of this tech in the first place.
Prerequisites are zero if you do this right. I can take a blank EC2 server, copy the binaries over and run them immediately. I don't even have to install any runtimes or SDKs.
Re: Ask HN: What would be your stack if you are building an MVP today?
#278The thing that bugs me the most with Next.JS and the whole JAMStack movement is that, yeah, you get from "git clone" to deployed on Vercel in two minutes, but if you need to create real app features like a sturdy admin, accounts, authorization, proper asset management, CI/CD, it takes a whole lotta time. I'm not even touching the most common app features. I'm speaking from experience, from building a Next.JS app for about a year.
Most Next apps out there are incomplete with the worst freaking user experience. Insert any other JS framework or hosting provider in the place of Next.JS and Vercel.
Of course, this is a generalisation, not all Next apps are that bad.
Using Rails is like a cheat-code in dev term.
Re: Ask HN: What would be your stack if you are building an MVP today?
#2792. Hosted Postgresql
3. Hosted Graphql API layer microservice (like hasura)
4. Hosted hhtps server
5. Some kind of cloud storage solution
5. Load-balancer ingress
6. Some kind of CDN
Spinnable in less than day with SSL on, works perfectly for any app to scale and covers most production problems
Re: Ask HN: What would be your stack if you are building an MVP today?
#280Earlier quoted context omitted.
At the core there is a custom crawler written in Rust, with the goal of eventually releasing it as an open source standalone application. But everything else, including scheduling the execution of this crawler, and parsing its output, is done on the Elixir monolith.
Would that be in Rust for performance reasons? Elixir IME isn't as slow as some other popular languages but it's no speed demon either.