Earlier quoted context omitted.
Maybe next js instead of supabase?
Next.js is more about frontend, but Supabase is more on backend. I cannot see any conflicts of the two, they can work with each other flawlessly.
Meant to say Nest.js sorry
Ask HN: What would be your stack if you are building an MVP today?
731–736 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#732Golang backend, Sveltekit frontend, and Openapi in-between with codegen on both ends to type it all (and document) throughout.
what codegen?
Re: Ask HN: What would be your stack if you are building an MVP today?
#733Earlier quoted context omitted.
This is unlikely to ever happen though since so much is tied to it like the permissions system and the admin. The ORM itself is central. I wouldn’t use Django unless your project depends on an RDBMS.
Even if not using a database, I will always reach for Django over a Flask or FastAPI. Yes, there is more boilerplate when just offering a few memory views, but there is so much ecosystem built around the tooling that the expense is worth it. Just making a form or sending an email from Flask requires a third party library which will never receive the level of maintenance as first-party Django. As an example, the often…
Fair. I'd probably reach for it too if I had any kind of frontend required, even if that were just HTML and forms. For server-only applications I'd probably go with FastAPI these days and I'm actually looking forward to an all-in-one framework that encompasses FastAPI as the core.
Re: Ask HN: What would be your stack if you are building an MVP today?
#734Well that depends a bit on what the MVP needs to be. Anything web related I'm probably going the Elixir/Phoenix route. I'm no web dev, but this combination makes me actually kind of like doing web-things with how batteries included it is, and the tools it provides to really jump start a project. Then I'd host it "old schoolish" in a VPS or similar since that's what I know best. Might consider being fancy and investig…
Agreed Elixir/Phoenix + Tailwind is at the sweet spot of scalability, performance, and bonkers productivity. Real time? Need to go distributed? Maximize # of features / developer bandwidth? Cutting edge machine learning training & model serving? Mobile? JSON APIs and GraphQL tooling is great, but https://github.com/liveviewnative is moving fast so this stack almost has the exodia of full stack, one language, and dist…
> Cutting edge machine learning training & model serving?
I am curious about this. Do you have more infos?
Re: Ask HN: What would be your stack if you are building an MVP today?
#735Svelte + Quarkus + Postgres
Re: Ask HN: What would be your stack if you are building an MVP today?
#736Building an MVP right now. My front-ends are primarily native mobile apps, because it's a video chat app. The website is simple React app. My backend is a custom/hybrid pattern I've been developing over the last few years which is primarily focused around CQRS + Event Sourcing + DDD. I have a single backend "command interface" (really just a single http endpoint that receives the name of a command + a data payload. t…
Hey, we've created an open-source framework that is really aligned with many of the points you’ve mentioned: CQRS + Event Sourcing + DDD.
Its name is Booster, it is built in TypeScript, and offers a minimalist approach to building event-sourced services, with a focus on reducing code and abstracting the infrastructure setup for a better developer experience. The framework generates a fully functional GraphQL API that's easily customizable and already used in several production projects. It's our go-to choice for new projects that fit the event-driven paradigm.
If you're interested, come join the conversation on our Discord channel at https://discord.gg/Rf6cwGRxgD, visit our website https://www.boosterframework.com/ or contribute to the project on GitHub at https://github.com/boostercloud/booster.