HN Explorer

Ask HN: What is your go-to stack for the web?

38 points by federalbob ↗ HN
Going back to the web after 10 years, I'm summoning the HN wisdom.

What is your go-to stack for a classic business web site ? for a Saas ? for a landing page ? for [whatever you do here] ?

73 comments

[ 4.3 ms ] story [ 157 ms ] thread
santiagobasulto
For SaaS, React in the frontend, Django + DRF in the backend. Postgres as DB. That's it.
Zanfa
Rails for SaaS/CRUD, haven’t done anything semi-static in a while, but would probably go with Webflow.
austin-cheney
Node, TypeScript, ESLint, Tauri, and a bunch of custom ESLint rules and a bunch of custom unit tests.
ssss11
Backend: Node with sqlite, Postgres or MySQL. Front: Vue with Bootstrap
throwaway94_30
I pick what I know best and "just works" because of my experience and the framework's maturity. YMMV

Backend: Spring Boot (Java or Kotlin depending on solo vs cooperation)

Frontend: React ("https://hilla.dev/" looks interesting, might try that next)

Database: Postgres

scns
Hilla looks great! Thanks.
rambambram
Mine is the CHAMP-stack. Consisting of CSS, HTML, Apache, MySQL and PHP.
lioeters
Is it all running on Linux by chance?
sam_lowry_
Probably not, because it will be LAMP otherwise.
rambambram
I have a hard time finding out if this is also some wordplay, like my own. But yes, it's running Linux at home and probably also at the webhost.
jfengel
What is Apache in this context? Tomcat?
rambambram
I don't know. Is Tomcat some version of Apache server? It says 'apache2' at my localhost while installing the server, and at the webhost I don't know (might be some other server that can run PHP). I usually don't dive deep into server territory, so I'm a lucky guy that I can focus on the design and the webdev.
jakopo87
Apache Tomcat is a web server for Java web applications, different from the Apache HTTP server (your 'apache2').
ivyirwin
For SaaS, React frontend and Laravel/Lumen on the backend. DB is usually Postgres.
romantomjak
Go, postgres, redis, vue, tailwind css. Been wanting to experiment with htmx, but haven’t gotten around to it yet.
irjustin
Pick what you know if you're going to build for a business. Me? Rails, Django and Postgres on AWS. Nowdays, Django on Lambda.

If you're building for fun, whatever you want!

pilgrim0
solid and tauri for apps, astro for content sites (with a headless cms if it’s big)
johrpan
Which headless CMS do you recommend?
skipchris
very small and indie, but i’ve really enjoyed SpinalCMS.
pilgrim0
Honestly? I dislike every single one and I avoid it when possible. It’s a matter of aligning the UX with the client’s preferences and expertise. Last project I used contentful, it has a lot of features, so it’s a good choice for a project which will scale.
baby
Rust and vuejs
albelfio
Sst.dev and remix.run are a pleasure to work with
INTPenis
Landing page and a business website can most likely be static, so AWS S3, Cloudfront, ACM, maybe a little lambda if necessary.

Services I tend to start with Flask, Celery, redis and build from there.

chr15m
Full stack ClojureScript on Sitefox with either Sqlite or Postgres, deployed to a VPS with Piku.
truckerbill
Mithril and xstate if it’s needed. Backend plain Go or Bun.

I don’t know why more people don’t use mithril

lgeorget
PHP and Symfony for the backend, Bootstrap for the frontend. Very classic. DB is MariaDB and Cassandra.

We also have many internal tools in R/Shiny.

jasfi
Next.js + PostgreSQL.

I also use Nim for when I need high-performance code, which can be utilized as a Node.js add-on using Denim.

michalg
Elixir, Phoenix LiveView, Postgres, TailwindCSS
coding123
Saas with a bit of data engineering mixed in: Mongo elastic react (nextjs) gql python spark LLM
nasir
Django: function based views.

UI: Django templates, htmx, tailwind, vanilla js or hypersceript, no build, no node, no npm. Avoiding writing js as much as possible.

Background workers: RQ with 3 priority queues

Deployment: Kamal one command deployment with underlying docker

Hosting: Linode server with backups

Storage: Mounted volume on the machine (maybe s3 eventually).

Benefits:

* High speed of iteration

* No boilerplate mess

* No build therefore no dealing with dependencies and npm rabbithole

* Fast deployment with Kamal (a bit of learning curve but once up just works)

* Much cheaper compared to PaaS. At least 50%.

* Multiple websites on the same instance

Of course I know django quite well so the goal is to remove as much friction as possible.

sam_lowry_
Postgrest + Petite-vue + One of the many classless css frameworks.
sam_lowry_
On a second though... Openresty would be my go-to choice for performance-critical parts of the backend.
fredwimberg
Backend: FastAPI + Pydantic + SQLModel (Python) Forntend: Vue/Nuxt Database: Postgres
assimpleaspossi
I ran a web dev business for 20 years. It includes two sites you probably have visited and bought things from. We used HTML for HTML. CSS for CSS and Javascript for Javascript.

Then we used a common and popular programming language to make them all work together.

It was compatible with everything. Worked everywhere. Interfaced with everything. And was as fast as hell.

No additional thinking or learning required.

ahofmann
Yes, exactly. And because all of this is bundled in laravel (and at some point I learned working with the framework), I'm using this since years for almost everything.
[deleted]
(comment deleted)