Ask HN: What would be your stack if you are building an MVP today?
SvelteKit + Supabase.<p>It’s the opposite of what a lot of people recommend. It’s not battle tested. Both of these technologies are still maturing BUT:<p>I can write everything in JS&#x2F;TS, I don’t have to get good at Ruby PHP or Python<p>Postgres is a great skill to learn.<p>Supabase is portable and can be self hosted, and its JS client is easy to use for DB manipulation and stuff like object storage.<p>For me, building a true full stack web app (not a todo list tutorial but something with real custom features) was going to be a learning process because I’ve been so heavily front end focused. So I decided to try to learn with the most modern tools available. It’s mostly worked out. I’ve had to ask for help on Discord a lot, especially with Supabase.<p>I have this idea for a blog post called “it’s just a CRUD app” that kind of challenges this idea that CRUD apps are brain dead simple. When you look at the myriad of options for building and deploying one. We’re talking like 50+ frameworks. Methodologies like dependency injection, micro service and monolith patterns. Yeah maybe it’s simple if you have been doing it for 15+ years and are comfortable with your stack but if you’re newer to the game, there’s a lot of complexity at play and the best choices for your situation are not obvious. Before moving to Supabase I was using NestJS because I was convinced I needed this framework with guard rails, but I hated it. So moving off that caused a lot of churn.<p>Edit: I also wanted to mention that the biggest split amongst all these recommendations IMO is how the backend and frontend interact with each other. Some of these frameworks will render frontend views for you. Then you&#x27;re dealing with a very classic web app. Then you hear other people in this thread talking about HTTP handlers, and it&#x27;s clear they&#x27;re talking about the backend existing as a REST API, which IMO is a bad pattern to use for your own app. REST APIs should be used for exposing your service to third parties.<p>But there&#x27;s a third way, that&#x27;s becoming popular amongst the &quot;bleeding edge&quot; with things like Next.js and SvelteKit that have a &quot;backend for frontend&quot; where they have to run a node&#x2F;deno based server anyways to do on demand SSR and hydrate. Having a separate backend, especially a separate backend that is just a REST API leads to a ton of redundant code and confusion.<p>So instead with ORMs like Prisma, people setting a persistent DB connection on this backend server and accessing&#x2F;manipulating the DB directly with some kind of client. I think this approach came to prominence alongside the rise of GraphQL. That&#x27;s basically the way Supabase works - they have a JS client and you interact with it in a similar way you would Prisma or TypeORM. They even have an article about how their client can be used in a similar enough way to GraphQL that it&#x27;s not worth using GraphQL instead.<p>Instead of traditional controllers where you would stash a lot of business logic (including authorization), the idea is you leverage PostgreSQL&#x27;s advanced features to help with that. I&#x27;m not a huge fan of this for multiple reasons. So you kind of have to make your own decisions on how much abstraction you&#x27;re going to put on top of their client.