3 ms·

Node is pretty viral in the "enterprise". My company is listed in the article and I've seen node sneak into big java projects, you know just to run unit tests f

Node is pretty viral in the "enterprise". My company is listed in the article and I've seen node sneak into big java projects, you know just to run unit tests for the frontend code. Then it takes on more and more responsibility until the project is a node project with a little java rather than a java project with a little node.

cheez 10y ago
Well when the options are Java and Node, even I would choose Node.
- eweise 10y ago
  I would choose Java. Java 8 with lambda functions and streams library, is a much more pleasant experience than previous versions. If you take the same library over framework approach with Java as you might with Node, you can build microservices just as easily, and docker equalizes the deployment effort. The main advantage I see with Node is working with JSON and a more simplistic concurrency model but to me Java is getting on the reactive bandwagon and beats Node by having more mature and stable libraries and by being statically typed.
  - Scarbutt 10y ago
    What Java libraries are you talking about in this case?
    - joshwa 10y ago
      Not OP, but Spring Boot and the Netflix stack (esp with rxjava) make it super easy to write fast, simple, non-blocking, easily-deployable, monitorable, and resilient microservices. Check out http://start.spring.io/ http://start.spring.io/ and click "switch to the full version" to see the huge variety of battle-tested libraries with excellent integration with Spring Boot.
    - latchkey 10y ago
      Jackson combined with JSOG is great. Resteasy as the endpoint layer with Guice as the DI framework. Project Lombok to remove the java boilerplate. Run that on AppEngine and you have an infinitely autoscaling application with zero downtime. Use Objectify for the ORM with the Datastore. =)
- kodablah 10y ago
  It's unfair to compare Java and Node. It's more fair to compare Java and JavaScript or JVM and Node. When the options are JVM or Node, I would choose the JVM. When the options are Java and JavaScript, I would choose Java. And when the options are something like Scala or TypeScript, I would choose Scala (because of the JVM vs Node, I love TypeScript). Of course, all of these choices are based on the use case, but I speak of server side apps here.

cheez 10y ago

Well when the options are Java and Node, even I would choose Node.

eweise 10y ago
I would choose Java. Java 8 with lambda functions and streams library, is a much more pleasant experience than previous versions. If you take the same library over framework approach with Java as you might with Node, you can build microservices just as easily, and docker equalizes the deployment effort. The main advantage I see with Node is working with JSON and a more simplistic concurrency model but to me Java is getting on the reactive bandwagon and beats Node by having more mature and stable libraries and by being statically typed.
- Scarbutt 10y ago
  What Java libraries are you talking about in this case?
  - joshwa 10y ago
    Not OP, but Spring Boot and the Netflix stack (esp with rxjava) make it super easy to write fast, simple, non-blocking, easily-deployable, monitorable, and resilient microservices. Check out http://start.spring.io/ http://start.spring.io/ and click "switch to the full version" to see the huge variety of battle-tested libraries with excellent integration with Spring Boot.
  - latchkey 10y ago
    Jackson combined with JSOG is great. Resteasy as the endpoint layer with Guice as the DI framework. Project Lombok to remove the java boilerplate. Run that on AppEngine and you have an infinitely autoscaling application with zero downtime. Use Objectify for the ORM with the Datastore. =)
kodablah 10y ago
It's unfair to compare Java and Node. It's more fair to compare Java and JavaScript or JVM and Node. When the options are JVM or Node, I would choose the JVM. When the options are Java and JavaScript, I would choose Java. And when the options are something like Scala or TypeScript, I would choose Scala (because of the JVM vs Node, I love TypeScript). Of course, all of these choices are based on the use case, but I speak of server side apps here.