23 engineers on Hacker News describe using Express.js first-hand: 4 endorse it, 2 regret it, 1 are mixed.
“We migrated our api server from flask Python to node-express-typescript.”
endorse · production · nojvek · 2023-07-20 · source ↗ · wrong label?“they are not generally just there, ready to use, and suitable for production.”
mixed · production · Tsarbomb · 2022-04-11 · source ↗ · wrong label?“We dabbled with NodeJS + Express which no one in the team liked to work on.”
regret · personal · blntechie · 2020-09-25 · source ↗ · wrong label?“The second, and bigger, thing that really bothered me about nodejs, and expressjs in particular, was the notion of back pressure is completely missing.”
regret · production · specialist · 2019-12-13 · source ↗ · wrong label?“"friendly, fast, and forgiving" is exactly how I've always found the Node/Express tooling and ecosystem to be”
endorse · production · throwanem · 2017-01-25 · source ↗ · wrong label?“We use node+express for everything at MileWise.”
endorse · production · nmeyer · 2012-12-16 · source ↗ · wrong label?“we use plain old Express at tldr.io... in the long-run I think we actually save time by knowing exactly what we do”
endorse · production · louischatriot · 2012-11-22 · source ↗ · wrong label?“with a seperate ExpressJS API (which others have used to make their own clients, like an Android app!)”
neutral · personal · varun_ch · 2023-12-22 · source ↗ · wrong label?“The express app is really only used during local dev. In prod, only the bot part is relevant.”
neutral · personal · badlogic · 2023-10-17 · source ↗ · wrong label?“we migrated from Express to NestJS, and it was an excellent decision.”
neutral · production · basicallybones · 2022-02-04 · source ↗ · wrong label?“the lambda itself is an express app with a single route defined”
neutral · production · retrocryptid · 2021-12-31 · source ↗ · wrong label?“I like Sveltekit's back end server better than Rails... and Express.”
neutral · personal · slantyyz · 2021-12-16 · source ↗ · wrong label?“we basically just have a normal Express app serving GraphQL.”
neutral · production · hn_throwaway_99 · 2021-11-20 · source ↗ · wrong label?“Sometimes the bottleneck could be in an Express middleware or in reading a massive Webpack manifest file”
neutral · production · eliseumds · 2019-12-31 · source ↗ · wrong label?“Rails or Express for the backend (depending on needs, I'll usually chose Rails over Express 90% of the time).”
neutral · production · jypepin · 2019-01-20 · source ↗ · wrong label?“Node/Express + Vue on the front end”
neutral · personal · newsbinator · 2018-12-08 · source ↗ · wrong label?“The nodejs version contains an expressjs reverse proxy to forward requests for things in the assets directory”
neutral · production · skrebbel · 2018-11-05 · source ↗ · wrong label?“Changing that to be actual pure Express functions and not use the cloud functions API was pretty easy and quick”
neutral · production · Nialna · 2018-09-11 · source ↗ · wrong label?“it was relatively easy for me to write a really simple Express server ... for local testing”
neutral · personal · Vinnl · 2017-12-21 · source ↗ · wrong label?“Express for basically everything HTTP.”
neutral · production · dfcowell · 2017-12-09 · source ↗ · wrong label?“We use Node.js with Express and some pretty simple but very effective middleware we wrote”
neutral · production · davismwfl · 2013-11-26 · source ↗ · wrong label?“Express benchmarks that I ran a few months ago were showing ~7k requests per second”
neutral · personal · notduncansmith · 2013-10-07 · source ↗ · wrong label?“I'm using socket.io, express, crypto module, etc.”
neutral · production · babuskov · 2012-08-09 · source ↗ · wrong label?