Elixir/Phoenix + Postgresql. Maximum comfort, minimum chore.
For frontend side, if i can get away with minimal js, i'd go that way. If not, highly depends on team and target interactivity. If it's just me, i'd go with LiveView
Ask HN: If you were to build a web app today what tech stack would you choose?
21–30 of 214 posts
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#22LAMP. It can easily be maintained by a single developer. Scales well enough for a decent number of users. Huge ecosystem of components. Easy to deploy to literally any web host. Wide variety of front-end systems. If you need to scale, it can do that. Developers for it are plentiful. But you can always rewrite it in the flavour-of-the-month framework when you hit either scale or money.
Agree but with Postgres instead
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#23Just had been thinking about this today, the current state of web development is making me seriously depressed.
I would pick what I'm most comfortable with, a simple monolithic Nest.js application running Fastify, with Postgres or SQLite, Dockerized, hosted on a predictably-priced host like Hetzner, and Ansible to automate everything. I know that stack will give me plenty of headroom until I eventually need to scale differently.
Front-end is still React, which has a massive ecosystem, and I feel like I can do _anything_ with it by just bringing in some dependencies, if it's a passion project then I want to deliver features fast, React allows me that.
I feel like a dinosaur, edge, workers, cloud functions... I'm familiar with none of that magic, there's probably a whole universe of amazing new ways to build for the web I'm sleeping on, but at that point I don't even care really.
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#24I have just launched a relatively straightforward webapp that required a light touch front end with fairly significant data processing on the backend
- Backend: Django (Postgres in production) + Celery to handle async tasks - Frontend: HTML (standard django renderer), CSS, HTMX + occasional jQuery - Deployment: Render
I was already familiar with Python and I feel the language is more than capable to handle the data processing required and with Django I could concentrate on the actual app functionality without diving too much into auth etc
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#25[deleted]
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#26Django + HTMX + SQLite or PostgreSQL
Hosted on a virtual machine.
... Or the stack you're most efficient/ effective in. A short time-to-market is most important for learning. If you don't reach an audience, your project might bore you soon. Tech rarely is the holy grail to success.
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#27Elixir with Liveview, or any server side you know well (in my case it’s Java/jsp) with Htmx.
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#28Depends on business scope, growth model etc. My default option is Java/Spring Boot/PostgreSQL for BE with HATEOAS API, Typescript/Angular SPA for FE if personalized experience is required. If it’s about just serving some almost static webpages, then some SSG+headless CMS with a bit of vanilla.js.
Choice of stack is simple: it may not be the best in class or fancy choice, but it’s close enough, allows simple infrastructure setup, quick start with rapid iterations and easy to go from 1 dev setup to a team. More importantly I have a lot of experience with this stack, so I can focus on business rather than on learning new technology.
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#29Frontend: Remix or Next.js with server components
Backend: ASP.NET Web API (REST). Only calling these APIs from the backend-for-frontend Node code.
Hosting: Everything at one Cloud provider, either Azure or AWS. No SaaS-services.
Database: Postgres
Infra: Terraform or Bicep for infratructure as code, and Docker.
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#30LAMP. It can easily be maintained by a single developer. Scales well enough for a decent number of users. Huge ecosystem of components. Easy to deploy to literally any web host. Wide variety of front-end systems. If you need to scale, it can do that. Developers for it are plentiful. But you can always rewrite it in the flavour-of-the-month framework when you hit either scale or money.
Which P?
Haha! As it's you, I'll say Python. But for me, PHP.