Home/ Questions/Q 8733985
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T09:45:19+00:00

I am watching node.js and its apps for a year now and I would

  • 0

I am watching node.js and its apps for a year now and I would love to replace bigger parts of my good old Java code with node.js.

The problem I noticed with node.js is that

  • it looks like a chaos, from version to version things don’t work anymore
  • bad documentation, really bad
  • no idea what libraries have been ported or will be ported any time soon
  • multi core managment, does it ?
  • uses 100% of the CPU power regardless of what it actually does (ie : pauses in loops). Thats not green and this is important to us.

Regarding security concerns I would put it behind a reverse proxy and only my old and real Java server would be able to use it.

update : funny this question gets closed because its not constructive. how can the question be constructive when I don’t have any glue? Thats why also I am aksing here ! You moderators here really suck sometimes.

However, would you rather suggest to wait before moving to node ? Or do you think its time to move over ?

I’m writing loads of Java server side code and I would start building my own base framework and then port piece by piece!?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Even if the questions gets closed:

    • Actually, it works pretty stable and backwards compatible so far
    • Are you for real ? –> http://nodejs.org/api/
    • Again: http://www.nodejs.org
    • Node didn’t scale with CPU or core numbers, you should let the OS scale node processes by just launching multiple instances
    • That is just wrong.

    Even if Node still is “young” in comparison to other “server-side considered languages”, it already found its place in a lot of spots. It can deal easily with huge amounts of users, it’s an excellent web-socket server counterpart, its lightning fast when it comes to dispatching network traffic to a lot active connections and its ECMAscript, the most sweet sugar language ever made (the last statement is personal opinion).

    There are probably hundreds of valid use cases for Node.js, obviously there is no specific task were it is a “must use”, but thats the same rule for any language most likely. Its fun, its fast, dig into it.

    • 0