Do I have product market fit? If so Go + Postregres either on EC2 or serverless depending on requirements. If I don't have product market fit and need to iterate as fast as possible then Node.js + Postgres. Probably a monolith unless there is a big advantage to making it serverless. Moving fast trumps everything else. Except for typescript, it doesn't really slow you down and might as well use ts-node until it's a scaling concern then you can worry about your build toolchain. Fastify for the framework. Probably ReactJS for the frontend. Answer from iends on reddit.com
🌐
Reddit
reddit.com › r/node › is node.js even considered for serious backend only development by companies anymore or is just bff/serverless only. are node.js jobs declining significantly?
r/node on Reddit: Is Node.js even considered for serious backend only development by companies anymore or is just BFF/serverless only. Are Node.js jobs declining significantly?
May 29, 2023 -

Compared to GO, Kotlin/Java, .net core etc. where job adverts for those languages are some serious backend ONLY job adverts and the entire (or majority) backend is FULLY in those languages.

When it comes to purely Node.js, it is most of the time NOT used to build entire backend and is often backend for frontend sitting in between acting as a proxy between frontend and other services written in better languages (companies words not mine).

And Node.js jobs are often coupled with react especially if next.js is used then due ssr and acting as both ssr and proxy (accumulating data). But even then Node.js/next combination is not the main stack in backend.

Regardless of whether next.js is used or not, a vast majority of jobs that i see with Node are niche like below.

  1. middlewares acting a data aggregators and fetching data from different services and node acts as backend for frontend only.

  2. next.js. everything from point 1 plus the ssr.

  3. They want you to do react and put node as well anyway as build tools are all in node (no corelation to backend) and incase they user next.js for ssr then also node is put.

  4. ONLY in serverless context Node.js is put.

So, is the usage of Node drying out wave are not companies NOT preferring Node.js in current times to build something new fully in Node.js?

Before people say, but my company use Node.js for xyz, please highlight whether they are recent project (or they were developed in Node.js during Node hype phase) and what percentage of entire backend is developed in Node?

Given the rise of similar posts on this sub asking same questions i.e "are companies still using Node.js" or "has Node.js work dried out and less jobs" or "Node.js jobs often require react etc" we can no longer ignore it and blaming it on current downturn in market. You dont see GO developers asking the for the same.

Thoughts?

Top answer
1 of 31
144
You can still find numerous companies running a full backend with Express/Fastify/Loopback (developed by IBM), even if some more performance sensitive endpoints and domains hand over to lower level languages. Node handles most things, but there will always be tasks a lower level systems language is more ideal for. Since Node builds on the language of web browsers, and has been selected by basically every “serverless”/FaaS (gross) provider, it’s ofc going to have a lot of popularity in these domains, as companies want to modernise but change as little as possible. My personal hypothesis is that as Node grows and matures, it’ll slowly start eating the pie of languages like C# and Java, just like it’s done for Ruby and Python. More and more companies are adopting Node for general server side and handing over to Rust/Go/C/C++ for stuff that must be fast. On the note of Go though, it seems like that language too is starting to decline, but that could just be what I’ve seen personally. The BBC use Node for their entire web publishing stack, a lot of their internal tools, and for APIs on their iPlayer and Sounds streaming apps. Although they do also still have a lot of Ruby and Java in older areas. GOV.UK Digital Identity (single sign on across UK government services) use Node.js to handle their front ends (they use bespoke SSR, akin to a traditional website) which then hands off to a AWS Lambda backend. Netflix primarily uses Node, handing over to Java only for core situations. PayPal have used Node since 2013 and continue to, although back-of-house financial systems are still in different languages. Trello, now an Atlassian (hiss) project, uses Node throughout its backend. Will you find a company using Node at every step? No. But that’s like using a hammer on concrete. There will always be tasks that require other languages, and companies ought to be (or continue to be) polyglot. However, Node has been growing and continues to grow.
2 of 31
32
I think Node.js is still quite relevant today and the usage will increase especially for fullstack development by folks that love JavaScript
🌐
Reddit
reddit.com › r/experienceddevs › is backend nodejs a dead end?
r/ExperiencedDevs on Reddit: Is Backend NodeJS a Dead End?
September 6, 2023 -

I got laid off from my last role of almost 6 years as a nodejs backend dev in january. i still have not found a new position. Looking at the # of job postings on zip recruiter now, i’m amazed how few jobs there are for remote nodejs. Is it dead? Almost every post mentions full stack or react. been doing nodejs almost 10 years

looking at last 5 days, remote. ~30 nodejs. ~100 c#. ~200 java. almost ~400 python. typescript has a bit more at ~60 but still seems pretty low.

do i just revert to a skill set from 6 years ago and pretend the last role didn’t happen? start from scratch on a new thing? I really have to find something soon.

edit: i’m not debating the performance or viability of the language for a project (i like nodejs and have many projects with it). i’m wanting to know about the viability of continuing a career in that space right now

Top answer
1 of 37
364
Wow there are some… interesting takes from people who are staff engineers here that leave me concerned. Node.js is not a dead end, because the point for most backend devs is not the framework you use. It is usually used when you want good I/o operations and concurrency to scale web apps, but does poorly with parallelism (concurrency and parallelism are NOT the same thing). That makes it great for crud apps and the like, but not great for cpu intensive tasks. In reality, it will be fine for 98% of all web development. However, I’d recommend taking a more language agnostic approach and not applying to just jobs that have node.js
2 of 37
163
5 years in tech is a lifetime. But it's just 1 lifetime You learn a lot, and you accomplish a lot in those 5 years. Problem is, it's just 1 lifetime. You'll go through many major tech/market shifts. Each one would feel like a lifetime on its own In your first 5 years, you can be a tech specialist. And it will get you very far in your career Most will squeeze the most out of being a tech specialist until their 10th year until they realize they're no longer progressing as much as before. In your 10th year, you definitely need to be tech agnostic already. In your first 5 years as a tech specialist, you were thriving. In the 2nd 5 years, you're surviving. But for your 3rd 5years? - very difficult to stay relevant. So in your 10th year moving forward, you need to be rebranding yourself as a problem solver (i.e. tech agnostic). Was your 2nd lifetime a waste then because you stayed a tech specialist? - no. Like it or not, you gained domain specialization as well. Use that to your advantage. For example, instead of calling yourself as a nodejs dev, call yourself as a fintech dev or health tech dev or whatever 😁
🌐
Reddit
reddit.com › r/node › node.js best practices - 2023 edition
r/node on Reddit: Node.js best practices - 2023 edition
July 25, 2023 -

What's new:

- A handful of new practices that relate to platform changes like ESM, EventTarget and more
- Tons of edits
- Recommended libraries for 2023
- Looking for new content only? just skim through the #new or #updated tags

https://github.com/goldbergyoni/nodebestpractices

🌐
Reddit
reddit.com › r/node › 2023: learn nest or keep learning express?
r/node on Reddit: 2023: Learn Nest or keep learning Express?
December 31, 2022 -

I have been working professionally as a Frontend for a year and I want to find my first job as 'Full-Stack'.

Do you recommend me to continue learning Express (with TS) or learn Nest?

🌐
Reddit
reddit.com › r/node › exploring the transition: from front-end to node.js backend development
r/node on Reddit: Exploring the Transition: From Front-End to Node.js Backend Development
August 21, 2023 -

Recently, I switched from Front-end development to Back-end development in NodeJS. After experiencing Backend development, I wouldn't want to go back to Front-end. I enjoy working with JavaScript and would prefer to continue coding in JS (or maybe TS). However, I often come across discussions highlighting the disadvantages of using JavaScript for Backend development compared to other programming languages. Personally, I haven't felt these issues yet, but I've only started a few months ago and haven't extensively worked with languages other than JS.

My question is whether these disadvantages are genuinely as serious as they're shown. What exactly are these disadvantages? (I've read about them already, but I'd appreciate understanding them in this context.) Would you choose to remain a JS Backend developer? Is there a substantial job market for Backend JS developers, or was I just fortunate?

🌐
Medium
medium.com › @Infowind › nodejs-for-backend-web-development-in-2023-2c3910ea0244
NodeJS for Backend Web Development in 2023 | by Infowind Technologies | Medium
May 1, 2023 - So there’s no doubt about the answer that NodeJS is insanely popular and will continue to be used for backend development in 2023 due to a surge in demand. Let’s decode it! Node.js is an intriguing combination of backend and frontend ...
Find elsewhere
🌐
Reddit
reddit.com › r/node › can i get a job as a node.js backend developer?
r/node on Reddit: Can I get a job as a Node.js backend developer?
February 16, 2025 -

I graduated in 2023 and am currently looking for a job. However, I see very few job openings for freshers in Node.js backend development. People keep telling me to learn frontend and become a full-stack developer, but I don’t enjoy frontend development. Every time I tried learning frontend, I failed because I struggle with CSS. Even though component libraries are available, I’m not very good at using them. I do understand core React.js, but frontend is not my strength.

My goal is to get a job as soon as possible, ideally within the next two months. What should I do to achieve this?

My current skill set:

  • Node.js, NestJS, Express

  • MySQL, PostgreSQL, MongoDB

  • AWS (S3, EC2)

  • GraphQL, Microservices

  • Kafka, Redis, Zod, and more

How can I maximize my chances of getting a backend developer job?

🌐
Reddit
reddit.com › r/webdev › poll: which back-end framework are you using in 2023?
r/webdev on Reddit: Poll: Which back-end framework are you using in 2023?
December 31, 2022 -

Bit of a cliche post, but given a new year is upon us, I'm curious what folks are planning to use for web back-ends in the coming year, particularly with respect to your professional endeavors (i.e., either currently going into next year, or for targeting new opportunities). Feel free to give more details in the comments in terms of particular frameworks within a given language, reason for use/selection, etc.

Thanks in advance for you responses and/or discussions, and Happy New Year to all!

(Editorial note: I ordered the poll options in alphabetical order to reduce "suggestiveness" or otherwise introducing my own personal bias. Furthermore, Reddit poll is limited to 6 total options, so I focused on the relatively "more popular" languages as the main choices, i.e., those which are relatively least likely to fall under the "Other" option.)

---

Edit/Erratum: I originally titled this post as "framework" but switched the semantics to "language" with respect to the poll options (without corresponding correction to title prior to submitting the post for creation, which unfortunately I cannot change/edit now), since there were only 6 total poll options available, which precludes breaking out into more granularity (i.e., in general there are many frameworks for a given language, which makes selecting 5 + 1 "other" = 6 total options quite challenging here, even if only focusing on top 2-3 most popular per language). Feel free to elaborate in the comments accordingly (e.g., you particular framework of choice for your poll selection).

🌐
Reddit
reddit.com › r/webdev › is node.js a good starting point to get into backend development?
r/webdev on Reddit: Is node.js a good starting point to get into backend development?
December 30, 2022 -

I feel that i have decent HTML, CSS and JavaScript along with some react skills. I want to get into backend development now and i was wondering if Node.js is a good way to start getting into backend development? This is my plan to dig into Backend,

  1. Node.js

  2. mySQL

  3. REST API

  4. PHP

What else would be critical to learn?

Top answer
1 of 7
4

I'd pick NodeJS and optionally React (for job opportunities). You don't need PHP (you need to learn Laravel as well) since you're already into JS, brush your skills on ES6 and maybe Typescript.

Also I encourage you to study OpenAPI spec if you're into backend and eventually GraphQL but not mandatory. Backend is super easy once you started tbh, scaling is super hard which shouldn't be your concern at this time.

Edit: just want to add, since you already have MySQL in your list, also slowly take time to learn 1 modern NoSQL/document database (I highly recommend SurrealDB for a hobby project).

2 of 7
4

I think JavaScript (NodeJS) is a great starting point, because it's the most popular language (gives you the most job opportunities). JavaScript is more popular for front-end, but still plenty of people use it for back-end with NodeJS. You can easily transition to other back-end languages later if you choose. You could also try TypeScript with NodeJS to see if you like it. I personally prefer C# for back-end over NodeJS, but I use them both a lot.

Every SQL flavor is extremely similar, so it doesn't matter which one you learn. If you're sticking with open-source, personally I like PostgreSQL much better than MySQL. From a job standpoint, SQL Server is the most popular, and you can get a free development-only version or use a dumbed-down version (Express) for commercial projects.

REST API is just a concept, you can do it in any language.

I personally would avoid PHP at all costs. There are fewer jobs in PHP compared to other languages and most programmers dislike PHP (but, a few like it).

For back-end, it would also be useful to learn cloud concepts, but not required. AWS is the most popular. Unfortunately, "cloud" encompasses A LOT and you'll probably only use 10% of it. Just learning what's available is useful, I wouldn't actually code anything in it until you need it for a job.

I think you could easily get a back-end job with just NodeJS+SQL, you don't need anything else.

P.S. I started a YT channel to teach coding by modding video games. Check it out and see if it's helpful to you.

https://www.youtube.com/@ai-gamer

🌐
Reddit
reddit.com › r/node › state of node.js performance 2023
r/node on Reddit: State of Node.js Performance 2023
May 16, 2023 - This is an amazingly thorough and detailed benchmark answering many questions I had about performance progress with NodeJS. Performance seems to be an important focus, especially with the recent rise of Bun.js (which I'd love to see updated benchmarks against it, too)
🌐
Reddit
reddit.com › r/node › node js backend course/resource recommendations for a frontend developer
r/node on Reddit: Node JS backend course/resource recommendations for a Frontend developer
November 28, 2023 -

Hello,

I am a front-end focused developer and would like to have a good understanding of the other half of the development "Backend".

I am not planing to switch to a backend role, but I would like to dip a toe at least in it. I hope if there is any recommended resource/course for Node JS backend suitable for a Frontend dev

🌐
Reddit
reddit.com › r/node › easiest way to deploy node app in 2023?
r/node on Reddit: Easiest way to deploy Node app in 2023?
February 7, 2023 -

What is the easiest way to host a Node.js api + MySQL/SQLite database in 2023?

I want as little setup as possible, don't want to edit giant config files, don't want "cool" features, don't want to deal with Docker, don't want to set up a Linux server — I just want to get it up and running.

I really like the dev experience of Cloudflare workers, but it is not NodeJS, unfortunately.

Any suggestions?

🌐
Reddit
reddit.com › r/node › what nodejs framework do you use in production?
r/node on Reddit: What NodeJS framework do you use in production?
May 14, 2023 -

Hi! I'm a relatively experienced developer (mostly backend) who used to work with Java applications, but have been working in the node environment for about 2 years now.

In this period I have worked with Express and Fastify services (and NestJS).

I'm about to start a new pet project and I'm curious what nodejs framework should I choose now.

  • I don't want to pick NestJS (mine is a small project and I use enough Nest in work).

  • Express seems to be declining in popularity?!

  • Fastify is fast, but I'm not sure how popular it is in production around the world.

My goal would be to practice a backend framework that is popular and desirable nowdays.

[EDIT]

Thank you all for your comments!

To clarify my intentions, I'm not at all against Express or any other framework and I will research and use the right tool for a job.

Right now I'm just curious what frameworks are the developers around the world are using in real life production nodejs backend apps.

For example, Koa and Adonis were totally new findinds for me and now I'm happy to check them out :)

🌐
Reddit
reddit.com › r/node › [deleted by user]
Is ONLY node js a good choice for backend?
January 30, 2025 - ... Yeah, there is, tho at least anecdotally, I see it pretty common in those projects too that fullstack devs are preferred. Not always, but increasingly often. ... Thank you for your good advice ! ... Node.js using typescript is a perfectly good backend runtime and language to use.
🌐
Reddit
reddit.com › r/node › is this a valid reason to give up node?
Is this a valid reason to give up node? : r/node
June 17, 2023 - There's a lot of Node jobs, sure, but are they true "backend" Node jobs? I think there's still a demand for Django and Rails devs everywhere, the only problem is, it's increasingly rarely going to be for the newest projects/greenfields, so you'll likely be joining teams with some legacy code, and all that can entail. ... I've found the Node ecosystem lacking in stuff I consider "basic bread and butter" of web development. Tell me about it! Add to it the JS/TS divide and you want to start pulling your hair.
🌐
Reddit
reddit.com › r/node › nodejs and backend development
r/node on Reddit: Nodejs and backend development
December 31, 2024 -

Is it possible to become a good backend developer using nodejs as a primary tool ? For some reason most of the big companies use c#, java and go for microservices, why is it so ?

Top answer
1 of 5
102
Where did you hear “most of the big companies”? FAANG use node. Fortune 500 use node. You can be a good programmer in any language;- The language isn’t what makes you a good software developer, it’s mastering the fundamentals of problem solving, which is completely independent of any programming language.
2 of 5
23
Node is as capable as essentially every other backend language. It’s particularly powerful for small companies because you can keep everyone working with the same language, but it’s also perfectly competent in a larger company that is more decoupled. In isolation, my recommended first backend language basically hinges on whether you want to do frontend/fullstack work. If so — Node is a great and efficient use of time, as you can just one language and drill really deep. If not — Go is extremely well done and likely the top pick. Python is nice and especially good for ML, but a lot of the tooling required to maintain projects at scale has only gotten good within the last five years or so, and as a whole IMO it’s good for prototyping but there are better options for large apps. Java is also quite nice nowadays (similar to Go in many fashions) but a lot of companies aren’t on new Java. Regardless of what you do — pick ONE language and drill deep on it. Way better to be 10/10 at one language and be able to pick out the common concepts that’ll apply anywhere, than 8/10 at two languages. Source — fullstack dev w/ backend focus by trade.