Live data from Hacker News

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

news.ycombinator.com

461–470 of 736 posts

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

#461

About a year ago I took off maybe 5 months to create a ephemeral voice messaging mobile app (Android + iOS) Stack: - React Native + Expo - Typescript - Supabase - Vercel - Some Vercel/nextJS-ish lamda functions so I could avoid AWS (Supabase didn't have that kind of offering yet) For me, it was _very_ pleasant to work in. I was able to ship features via OTA updates from idea to live in literally minutes.. sometimes e…

How did you define your models and manage database migrations with Supabase?

After things were live, my migrations would be backward compatible. It's also possible to organize your tables where most of your data is in private schemas, and public views serve as your apis and versioning. Anything in a public view must be treated as a long-lived API until clients can be phased out.

My userbase was in the dozens at most, so pushing out a version OTA usually was effective to get things moving along.

Worst case, I had some code to check if the client version was too old and would shut it down until they updated.

As per models, what kind of details are you asking?

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

#462
Currently building an MVP:

- NodeJS, Typescript, Docker

- Fastify for the API

- Sequelize for ORM (Prisma seems like a good choice too but comes with too many features imo)

- Postgres (locally rn)

- AtlasDB for migration (I like the declaration style)

- Hosting didn't choose yet but would go with vercel or free tier GCP

Im proefficient with JS so that explains the why, however in 10 years the ecosystem still didn't catch with Rails in term of having one solution to all problems.

You still have to carefully choose your dependencies, all tutorials are quickly outdated and it's missing some crucial pieces that you have to glue manualy or code entirely.

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

#463
post #462

Currently building an MVP: - NodeJS, Typescript, Docker - Fastify for the API - Sequelize for ORM (Prisma seems like a good choice too but comes with too many features imo) - Postgres (locally rn) - AtlasDB for migration (I like the declaration style) - Hosting didn't choose yet but would go with vercel or free tier GCP Im proefficient with JS so that explains the why, however in 10 years the ecosystem still didn't c…

Prisma has screwed me too many times to count. Sequelize has always been solid.

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

#464
post #426

Earlier quoted context omitted.

I honestly cannot believe that Rails doesn't have this built in. This was something that was in Django for as long as I can remember; I was looking at it in I think 2006 and it existed at that point in a very similar state to what I've seen lately. Not a dig on Rails, like "Oh, Rails is so bad they don't even have..."; rather, Rails is extremely capable, and so are Rails devs, so I legitimately don't understand why t…

Rails has Active Admin which is equivalent to what you get with Django. It's just not a core Rails gem but it's one line in your Gemfile to add it.

Whoah I never knew that - or maybe did but never seriously considered it. It's been my biggest surface-level gripe with Rails compared to Django so thank you very much for bringing it up

Edit: and it' still maintained !

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

#465
Fully custom runs anywhere stack, hand written OS, orchestrator, VMM and TLS*

*bearSSL powered because I can't into curves myself :/ as the only external dep

if state is needed I lean on DuckDb but eventually a more optimized in-memory columnar data structure will be devised.

Mostly because I found all the other options in this space to be lacking for performance-oriented low latency services.

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

#466

Earlier quoted context omitted.

I honestly cannot believe that Rails doesn't have this built in. This was something that was in Django for as long as I can remember; I was looking at it in I think 2006 and it existed at that point in a very similar state to what I've seen lately. Not a dig on Rails, like "Oh, Rails is so bad they don't even have..."; rather, Rails is extremely capable, and so are Rails devs, so I legitimately don't understand why t…

To be fair, Django only caught up with Rails in the past 5 years. When I started with Django it didn't have basic stuff that Rails had, such like auto database migrations and the Rails asset pipeline. The database migration stuff really helps when building/iterating. The Django middleware was very finky at the time.

FWIW, Django has built in migrations since 1.7 which was released in Sep/2014.

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

#467
After working with the PETAL (Phoenix, Elixir, TailwindCSS, Alpine.Js, Liveview) stack at $JOB for a while now, I have to say I've never been more productive.

Early on I would still have to lean on Alpine heavily for various JS interactions but with all the features Liveview has been adding and improving on (Hello JS module!) I find myself needing it less and less. Liveview really has been a game changer for me. Tailwind has more or less fixed most of my frustrations with CSS and has worked itself nicely into the company design system resulting in nice re-usable components that can be easily customized for those one-offs. Elixir is a nice language to use and I find myself missing features of it when working with other languages. Phoenix is well structured for projects and the newer generators solve a lot of common issues/features in projects like user auth in a reasonable way.

Depending on the needs of the app I'd look into deploying to Fly.io otherwise I've been using Kubernetes with little issue. I've toyed with Nomad for orchestration but haven't used it enough to give an opinion. I do wander if it's a nice middle ground for those who don't need the full suite of what K8s offers.

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

#468
Backend

.NET Core on Linux - Works really well, C# is a great language and quite performant too.

EKS/ECS on AWS with spot instances - works out pretty cheap

Cloud DBs like Aurora or DynamoDB

React for frontend, because of how many libraries are easy to get for it.

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

#469

Earlier quoted context omitted.

The biggest benefit to Django, in my opinion, is the orm and admin tooling. Being able to fix things in your app without having to open a repl or open a database tool is absolutely killer.

I honestly cannot believe that Rails doesn't have this built in. This was something that was in Django for as long as I can remember; I was looking at it in I think 2006 and it existed at that point in a very similar state to what I've seen lately. Not a dig on Rails, like "Oh, Rails is so bad they don't even have..."; rather, Rails is extremely capable, and so are Rails devs, so I legitimately don't understand why t…

There's a handful of very capable and mature admin solutions (activeadmin, rails_admin, administrate, and still people coming up with new ideas, see avo and madmin as newer examples), they just haven't had one become bundled mainline.

Similar situation with authentication, where devise has been a mainstay for over a decade, but it's not always the best fit for everybody so core rails still just has the basic plumbing to build it yourself (with the low-level has_secure_password).

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

#470
Some of my assumptions - meet customers where they are (need apps & web), be able to iterate quickly, minimize tech skills required, prefer easy-to-hire skills, worse is better (imperfect decisions are necessary to go fast & get customer feedback), prefer batteries-included frameworks.

Given my background that means .NET Maui Blazor (aka Maui Hybrid). You need two skills: C# and HTML (Razor). One language on the front end and back end. Compiles to native code on iOS, Android, Mac, and PC; WebAssembly in the browser. On the native apps the HTML UI is interpreted, but the rest of the code is in-process and native.

Since I want to use .NET, that means the best cloud support is Azure. Azure Functions for the API - serverless for frugal startup costs. For data store, Cosmos DB in NoSQL mode as a JSON documentDB - again, serverless for frugal startup costs.

I'm also very intrigued with using Go and Flutter instead of MAUI, but given my background that means a learning curve instead of being productive with a language I know well. I think C# and HTML are easier (more abundant) skills to hire, but I suspect Go and Flutter would attract more open-source-aware developers.

I'm not sure about a front-end HTML framework to go with Blazor. It ships with Bootstrap, which is probably file. I'm curious about Bulma which looks simpler and Material 3.0 for Web which is in alpha and marching toward 1.0 release soon.

Post reply on HN