Comparison between nodejs and spring MVC

HI,
I want to understand the difference between nodejs and spring.
Is spring going to be replaced totally with nodejs in coming future ?
Is nodejs a better and advanced way to write web applications ?

Thanks
Rohit BajajAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gary DavisDir Internet SvcsCommented:
They are very similar. See this comparison chart:

http://vschart.com/compare/node-js/vs/spring-framework

Spring is from 2002 and Node.js is 2015.
gurpsbassiCommented:
Nodejs is not a replacement for spring MVC.

You could say the same about Scala and Java. It's not a replacement for Java.

I've used nodejs in the past to power my web front end but still talking to spring controllers over REST.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
dpearsonCommented:
For me the major difference is the underlying language.

NodeJS is obviously JavaScript.
Spring is Java.

With that each gets certain strengths and weaknesses - so the choice should depend on the application.

Some of the pros and cons I see:

JavaScript:
 - Faster to get up and running (less 'ceremony')
 - Same language for backend and front end development so single skill set
 - Dynamic language flexibility
 - Flip side of dynamic language is the lack of strong typing - so typically harder to integrate and maintain large, complex systems.

Java:
  - High performance
  - Very well understood solutions to problems
  - Huge, skilled developer base
  - Strong typing - so less flexible, but better at large scale

So my general sense would be - if the project is "smaller scale" NodeJS is a natural fit.  If the project is "larger scale" then Spring may be better.  Fortunately "small" vs "large" are poorly defined - so lots of room for personal preferences.

But they don't seem targeted at exactly the same problem domain, so seems unlikely that NodeJS simply replaces Spring (or other Java frameworks) long term.

Doug
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java

From novice to tech pro — start learning today.